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.
