On Thu, 2007-06-28 at 15:16 -0400, Tom Lane wrote:
> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> > AFAICS, we can just simply remove the assertion. But is there any
> > codepaths that assume that after calling HeapTupleSatisfiesSnapshot, all
> > appropriate hint bits are set?
> There had better not be, since we are going to postpone setting hint
> bits for recently-committed transactions as part of the async-commit
> A quick grep suggests that VACUUM FULL might be at risk here.
No we're clear: I caught that issue specifically for VACUUM FULL fairly
early on. VF assumes all hint bits are set after the first scan, so we
flush prior to the scan to ensure its safe to set the hint bits. There
are no concurrent hint bit setters, so we are good.
In response to
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2007-06-28 22:15:28|
|Subject: Re: lazy vacuum sleeps with exclusive lock on table|
|Previous:||From: Alvaro Herrera||Date: 2007-06-28 21:16:54|
|Subject: lazy vacuum sleeps with exclusive lock on table|