Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?
Date: 2011-09-21 19:02:34
Message-ID: CAHyXU0ya=SqRBVS8TGN8aV4-NO+8OEhdLkBnWFJSs3P=L+gMRg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 21, 2011 at 1:03 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> Hi,
>
> I notice that HeapTupleSatisfiesToast is not setting the
> HEAP_XMIN_COMMITTED bit, though it is reading it.  Is there a reason for
> this?  It seems to me that it'd make sense to have it set ... unless
> it's set by some other routine, somehow?

I think it's implied from the untoasted row. Notice that it's not
checking visibility either except in binary upgrade cases.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-09-21 19:08:29 Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
Previous Message Kevin Grittner 2011-09-21 18:48:17 Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)