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.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Alvaro Herrera||Date: 2007-06-28 19:29:48|
|Subject: Re: SetBufferCommitInfoNeedsSave and race conditions|
|Previous:||From: Tom Lane||Date: 2007-06-28 19:09:38|
|Subject: Re: write past chunk end in ExprContext / to_char |