| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Pre-set Hint bits/VACUUM FREEZE on data load..? |
| Date: | 2011-03-25 20:26:30 |
| Message-ID: | 4D8CFA76.8060900@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25.03.2011 22:21, Robert Haas wrote:
> On Fri, Mar 25, 2011 at 3:29 PM, Greg Stark<gsstark(at)mit(dot)edu> wrote:
>> On Fri, Mar 25, 2011 at 7:06 PM, Robert Haas<robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2011-03-25 20:31:20 | Problem with streaming replication, backups, and recovery (9.0.x) |
| Previous Message | Robert Haas | 2011-03-25 20:22:48 | Re: SSI bug? |