Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Thu, 28 Jun 2007 15:16:15 -0400
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
- Follow-Ups:
- Re: SetBufferCommitInfoNeedsSave and race conditions
- From: Simon Riggs
- Re: SetBufferCommitInfoNeedsSave and race conditions
- From: Alvaro Herrera
- Re: SetBufferCommitInfoNeedsSave and race conditions
- References:
- SetBufferCommitInfoNeedsSave and race conditions
- From: Pavan Deolasee
- Re: SetBufferCommitInfoNeedsSave and race conditions
- From: Heikki Linnakangas
- SetBufferCommitInfoNeedsSave and race conditions
- Prev by Date: Re: write past chunk end in ExprContext / to_char
- Next by Date: Re: SetBufferCommitInfoNeedsSave and race conditions
- Previous by thread: Re: SetBufferCommitInfoNeedsSave and race conditions
- Next by thread: Re: SetBufferCommitInfoNeedsSave and race conditions
- Indexes: