Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse
Дата
Msg-id CAB7nPqTQTRi0JmRUX_j=3rt0+kBPAW7EKPQRWoyjGwid98hZ+w@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Ответы Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse
Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse
Список pgsql-bugs
_

On Wed, Jul 6, 2016 at 12:56 PM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
>>>>>> "Michael" == Michael Paquier <michael.paquier@gmail.com> writes:
>
>  >> When creating a physical replication slot, the catalog_xmin field of
>  >> the new slot is not initialized. If the slot storage had previously
>  >> been used for a logical slot, the old catalog_xmin will remain in
>  >> place and interfere with vacuum.
>
>  Michael> Good catch! The same applies to confirmed_flush_lsn, which is
>  Michael> used only by logical decoding and should remain as NULL for
>  Michael> physical slots.  So I propose the patch attached to address
>  Michael> both problems.
>
> What about slot->effective_catalog_xmin ?

Yes. I guess so, as well as the other candidate_* fields in the slot
to begin from a clean state.
--
Michael

Вложения

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

Предыдущее
От: Andrew Gierth
Дата:
Сообщение: Re: BUG #14228: replication slot catalog_xmin not cleared on slot reuse
Следующее
От: Oskari Saarenmaa
Дата:
Сообщение: Re: BUG #14150: Attempted to delete invisible tuple