Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?
Дата
Msg-id CAHyXU0ya=SqRBVS8TGN8aV4-NO+8OEhdLkBnWFJSs3P=L+gMRg@mail.gmail.com
обсуждение исходный текст
Ответ на HeapTupleSatisfiesToast not setting XMIN_COMMITTED?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?
Список pgsql-hackers
Дерево обсуждения 
On Wed, Sep 21, 2011 at 1:03 PM, Alvaro Herrera <alvherre@alvh.no-ip.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

В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
Следующее
От: Robert Haas
Дата:
Сообщение: Re: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)