Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
Дата
Msg-id CAA4eK1KcgV+FbG+RQLHnDTqMOS7g6fn=U289-+0FnUPjLmf8Mg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL  (Sergei Kornilov <sk@zsrv.org>)
Ответы RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
Список pgsql-hackers
On Tue, Jul 11, 2023 at 2:17 PM Sergei Kornilov <sk@zsrv.org> wrote:
>
> I think it's appropriate to add on the restrictions page. (But mentioning that this restriction is only for
subscriber)
>
> If the list were larger, then the restrictions page could be divided into publisher and subscriber restrictions. But
notfor one very specific restriction. 
>

Okay, how about something like: "The UPDATE and DELETE operations
cannot be applied on the subscriber for the published tables that
specify REPLICA IDENTITY FULL when the table has attributes with
datatypes (e.g point or box) that don't have a default operator class
for Btree or Hash. This won't be a problem if the table has a primary
key or replica identity defined for it."?

--
With Regards,
Amit Kapila.



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

Предыдущее
От: Amit Langote
Дата:
Сообщение: Re: generic plans and "initial" pruning
Следующее
От: "Jonathan S. Katz"
Дата:
Сообщение: Re: Incremental sort for access method with ordered scan support (amcanorderbyop)