Re: Add a GUC variable that control logical replication

From: Quan Zongliang <zongliang(dot)quan(at)postgresdata(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add a GUC variable that control logical replication
Date: 2019-09-18 09:33:44
Message-ID: 9b9f05e2-2108-ef3b-3d16-a82ac1158942@postgresdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019/9/18 17:11, Peter Eisentraut wrote:
> On 2019-09-18 10:39, Quan Zongliang wrote:
>> Sybase has a feature to turn off replication at the session level: set
>> replication = off, which can be temporarily turned off when there is a
>> maintenance action on the table. Our users also want this feature.
>
> These kinds of feature requests are always dubious because just because
> Sybase behaves this way for some implementation or architectural reason
> doesn't necessarily mean it makes sense for PostgreSQL too.
>
Agree
> 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.
My English is bad that I use the wrong word “maintenance” in my description.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dmitry Dolgov 2019-09-18 09:59:36 Re: [HACKERS] [PATCH] Generic type subscripting
Previous Message Peter Eisentraut 2019-09-18 09:16:35 Re: some PostgreSQL 12 release notes comments