Re: [PATCH] Logical decoding of TRUNCATE

Поиск
Список
Период
Сортировка
От Petr Jelinek
Тема Re: [PATCH] Logical decoding of TRUNCATE
Дата
Msg-id 3952d6e6-f438-f393-9a02-aae871d2fc3e@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [PATCH] Logical decoding of TRUNCATE  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [PATCH] Logical decoding of TRUNCATE
Список pgsql-hackers
On 24/01/18 13:50, Peter Eisentraut wrote:
> I wonder whether this should be dealing with sequences at all.  We are
> not currently publishing any information about sequences, so it seems
> weird to do it only here.  Also, I'd imagine that if we ever get to
> publishing sequence events, then the sequence restarts would be
> published as independent events.
> 

That depends on if we consider this to be part of sequence handling or
truncate statement replication handling. It's true that if we had
sequence replication, the restart would get propagated that way anyway.
OTOH, if we'll want to add option in the future to propagate cascade (to
any additional tables on downstream), it may need to reset sequences
which are not even present upstream and as such would not be handled by
sequence replication.

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services


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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [PATCH] Logical decoding of TRUNCATE
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory