Re: logical decoding - GetOldestXmin

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: logical decoding - GetOldestXmin
Дата
Msg-id CA+TgmoZFBgE8FMwONw9GY=s5CnFNksXCnfkWet2oi_XYMqG-rw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: logical decoding - GetOldestXmin  ("anarazel@anarazel.de" <andres@anarazel.de>)
Ответы Re: logical decoding - GetOldestXmin
Список pgsql-hackers
On Tue, Dec 18, 2012 at 5:25 PM, anarazel@anarazel.de
<andres@anarazel.de> wrote:
> The problem is that at the time GetSnapshotData returns the xmin horizon might have gone upwards and tuples required
fordecoding might get removed by other backends. That needs to be prevented while holding the  procarray lock
exclusively.

Well, for the ordinary use of GetSnapshotData(), that doesn't matter,
because GetSnapshotData() also updates proc->xmin.  If you're trying
to store a different value in that field then of course it matters.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Noah Misch
Дата:
Сообщение: Re: system administration functions with hardcoded superuser checks
Следующее
От: Robert Haas
Дата:
Сообщение: Re: system administration functions with hardcoded superuser checks