Skip site navigation (1) Skip section navigation (2)

Re: SetBufferCommitInfoNeedsSave and race conditions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SetBufferCommitInfoNeedsSave and race conditions
Date: 2007-06-28 19:16:15
Message-ID: 19267.1183058175@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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
patch.

A quick grep suggests that VACUUM FULL might be at risk here.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-06-28 19:29:48
Subject: Re: SetBufferCommitInfoNeedsSave and race conditions
Previous:From: Tom LaneDate: 2007-06-28 19:09:38
Subject: Re: write past chunk end in ExprContext / to_char

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group