Tom Lane escribió:
> Heikki Linnakangas <[EMAIL PROTECTED]> 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
> patch.
> A quick grep suggests that VACUUM FULL might be at risk here.

That particular case seems easily fixed since VACUUM FULL must hold an
exclusive lock; and we can forcibly set sync commit for VACUUM FULL.

Alvaro Herrera                      
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to