Horton

Re: BUG #14941: Vacuum crashes

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>, "Bossart, Nathan" <bossartn@amazon.com>, Masahiko Sawada <sawada.mshk@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-01-09T21:46:55Z
Lists: pgsql-bugs, pgsql-hackers 
On 2018-01-09 10:23:12 -0500, Robert Haas wrote:
> On Mon, Jan 8, 2018 at 11:27 PM, Michael Paquier
> <michael.paquier@gmail.com> wrote:
> > On Thu, Dec 28, 2017 at 10:46:18PM +0000, Bossart, Nathan wrote:
> >> I agree, this makes more sense.  I've made this change in v3 of 0003.
> >
> > Based on the opinions gathered on this thread, 0001 and 0002 seem to be
> > in the shape wanted, and those look good for shipping.
> 
> Committed 0001.

FWIW, I think in the future it'd be good to develop new features outside
of a thread about "vacuum crashes".

Greetings,

Andres Freund

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.