Re: BUG #14941: Vacuum crashes - Mailing list pgsql-hackers

From Andres Freund
Subject Re: BUG #14941: Vacuum crashes
Date
Msg-id 20180306015854.icrxs7vnj5teoqzp@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #14941: Vacuum crashes  (Andres Freund <andres@anarazel.de>)
Responses Re: BUG #14941: Vacuum crashes  ("Bossart, Nathan" <bossartn@amazon.com>)
Re: BUG #14941: Vacuum crashes  ("Bossart, Nathan" <bossartn@amazon.com>)
List 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


pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Re: BUGFIX: standby disconnect can corrupt serialized reorder buffers
Next
From: Peter Geoghegan
Date:
Subject: Re: Faster inserts with mostly-monotonically increasing values