Re: BUG #14941: Vacuum crashes
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: "Bossart, Nathan" <bossartn@amazon.com>, 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-03-06T01:58:54Z
Lists: pgsql-bugs, pgsql-hackers
On 2018-03-03 16:12:52 -0800, Andres Freund wrote: > On 2018-01-11 08:14:42 +0900, Michael Paquier wrote: > > On Wed, Jan 10, 2018 at 05:26:43PM +0000, Bossart, Nathan wrote: > > > Perhaps any logging changes for VACOPT_NOWAIT could be handled in a > > > separate thread. For now, I've updated 0003 to remove the logging > > > changes. > > > > Thanks. I am marking those as ready for committer, you are providing the > > set patch patch which offer the most consistent experience. > > I was working on committing 0002 and 0003, when I noticed that the > second patch doesn't actually fully works. NOWAIT does what it says on > the tin iff the table is locked with a lower lock level than access > exclusive. But if AEL is used, the command is blocked in I've pushed the first one now. There seems to be no reason to wait with it, even it takes a bit till we can get the second part right. - Andres
Commits
-
Add option SKIP_LOCKED to VACUUM and ANALYZE
- 803b1301e8c9 12.0 landed
-
Rename VACOPT_NOWAIT to VACOPT_SKIP_LOCKED
- edc6b41bd4a8 12.0 landed
-
Add parenthesized options syntax for ANALYZE.
- 854dd8cff523 11.0 landed
-
Don't allow VACUUM VERBOSE ANALYZE VERBOSE.
- 921059bd66c7 11.0 landed
-
Fix inadequate locking during get_rel_oids().
- 19de0ab23ccb 11.0 cited
-
Avoid having autovacuum workers wait for relation locks.
- 32896c40ca76 9.1.0 cited