Horton

Re: BUG #14941: Vacuum crashes

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: "Bossart, Nathan" <bossartn@amazon.com>
Cc: Andres Freund <andres@anarazel.de>, Masahiko Sawada <sawada.mshk@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Lyes Ameddah <lyes.amd@gmail.com>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.org>
Date: 2018-04-06T02:47:53Z
Lists: pgsql-bugs, pgsql-hackers 
On Fri, Apr 06, 2018 at 06:41:14AM +0900, Michael Paquier wrote:
> That would be wiser.  We are two days away from the end of the CF and
> this patch gets quite invasive with a set of new concepts, so my
> recommendation would be to do so.  There has been already much done with
> the introduction of the new grammar for ANALYZE, and the introduction of
> RangeVarGetRelidExtended().

By the way, let's do that on a new thread next time :)
--
Michael

Commits

  1. Add option SKIP_LOCKED to VACUUM and ANALYZE

  2. Rename VACOPT_NOWAIT to VACOPT_SKIP_LOCKED

  3. Add parenthesized options syntax for ANALYZE.

  4. Don't allow VACUUM VERBOSE ANALYZE VERBOSE.

  5. Fix inadequate locking during get_rel_oids().

  6. Avoid having autovacuum workers wait for relation locks.