Re: Pre-set Hint bits/VACUUM FREEZE on data load..? - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Pre-set Hint bits/VACUUM FREEZE on data load..?
Date
Msg-id 4D8CFA76.8060900@enterprisedb.com
Whole thread Raw
In response to Re: Pre-set Hint bits/VACUUM FREEZE on data load..?  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 25.03.2011 22:21, Robert Haas wrote:
> On Fri, Mar 25, 2011 at 3:29 PM, Greg Stark<gsstark@mit.edu>  wrote:
>> On Fri, Mar 25, 2011 at 7:06 PM, Robert Haas<robertmhaas@gmail.com>  wrote:
>>>> 1. The table has been created or truncated in the same transaction
>>> ,,,
>>> That's not enough... some other transaction could see the data before
>>> the transaction commits.
>>
>> How?
>
> Hmm.  Maybe I'm wrong.  I guess the XID would still be in the MVCC
> snapshot of every other running transaction, so maybe it would be OK.
> *scratches head*

Right. You can't mark the tuples as frozen, but you can set the 
xmin-committed hint bits.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: SSI bug?
Next
From: hubert depesz lubaczewski
Date:
Subject: Problem with streaming replication, backups, and recovery (9.0.x)