"Kevin Grittner" wrote:
> So now that I'm sure we actually do need code there, I'll add it.
In working on this I noticed the apparent need to move two calls to
PredicateLockTuple a little bit to keep them inside the buffer lock.
Without at least a share lock on the buffer, it seems that here is a
window where a read could miss the MVCC from a write and the write
could fail to see the predicate lock. Please see whether this seems
> And I'll add the new test to the isolation suite.
We don't need all permutations for this test, which is a good thing
since it has such a long setup time. Is there an easy way to just
run the one schedule of statements on three connections?
pgsql-hackers by date
|Next:||From: Cédric Villemain||Date: 2011-02-05 21:19:39|
|Subject: Re: limiting hint bit I/O|
|Previous:||From: Cédric Villemain||Date: 2011-02-05 20:34:15|
|Subject: Re: We need to log aborted autovacuums|