Re: Add a GUC variable that control logical replication
От
Peter Eisentraut
Тема
Re: Add a GUC variable that control logical replication
Дата
Msg-id
0ece7afe-ee5b-d3f6-31b7-363023a88880@2ndquadrant.com
Ответ на
Re: Add a GUC variable that control logical replication (Euler Taveira)
Список
Дерево обсуждения
Add a GUC variable that control logical replication Quan Zongliang <zongliang.quan@postgresdata.com>
Re: Add a GUC variable that control logical replication Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Add a GUC variable that control logical replication Quan Zongliang <zongliang.quan@postgresdata.com>
Re: Add a GUC variable that control logical replication Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Add a GUC variable that control logical replication Euler Taveira <euler@timbira.com.br>
Re: Add a GUC variable that control logical replication Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: Add a GUC variable that control logical replication Quan Zongliang <zongliang.quan@postgresdata.com>
Re: Add a GUC variable that control logical replication Michael Paquier <michael@paquier.xyz>
Re: Add a GUC variable that control logical replication Craig Ringer <craig@2ndquadrant.com>
Re: Add a GUC variable that control logical replication Craig Ringer <craig@2ndquadrant.com>
On 2019-10-20 00:23, Euler Taveira wrote: >> You can probably achieve that using ALTER PUBLICATION to disable >> publication of deletes or truncates, as the case may be, either >> permanently or just for the duration of the operations you want to skip. >> > ... then you are skipping all tables in the publication. You can group tables into different publications and set the subscription to subscribe to multiple publications if you need this kind of granularity. In any case, this kind of thing needs to be handled by the decoding plugin based on its configuration policies and depending on its needs. For example, let's say you have two decoding plugins running: one for a replication system and one for writing an audit log. It would not be appropriate to disable logging for both of them because of some performance optimization for one of them. And it would also not be appropriate to do this with a USERSET setting. If we need different hooks or more DDL commands do this better, then that can be considered. But this seems to be the wrong way to do it. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления