| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Quan Zongliang <zongliang(dot)quan(at)postgresdata(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add a GUC variable that control logical replication |
| Date: | 2019-10-19 17:10:53 |
| Message-ID: | f1890130-8be3-5a63-46f5-b75af36b656b@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-09-18 11:33, Quan Zongliang wrote:
> On 2019/9/18 17:11, Peter Eisentraut wrote:
>> Why do you need to turn off replication when there is "maintenance" on a
>> table? What does that even mean?
>>
> In a table, the user only keep data for a period of time and delete
> expired records every day, involving about 10 million to 20 million
> records at a time. They want to not pass similar bulk operations in
> logical replication.
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2019-10-19 17:36:25 | Re: Backport "WITH ... AS MATERIALIZED" syntax to <12? |
| Previous Message | Peter Eisentraut | 2019-10-19 16:51:33 | Re: Fix most -Wundef warnings |