| 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-09-18 09:11:02 |
| Message-ID: | 79a88441-45cf-e9d5-917b-fa3e2d28d1b3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Why do you need to turn off replication when there is "maintenance" on a
table? What does that even mean?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-09-18 09:16:35 | Re: some PostgreSQL 12 release notes comments |
| Previous Message | Juan José Santamaría Flecha | 2019-09-18 09:09:52 | Re: Allow to_date() and to_timestamp() to accept localized names |