| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SUBSCRIPTIONS and pg_upgrade |
| Date: | 2017-04-14 01:55:19 |
| Message-ID: | 8d89d0ec-227d-7f1a-de56-69162d690404@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/13/17 12:11, Robert Haas wrote:
> I wonder if we should have an --no-subscriptions option, now that they
> are dumped by default, just like we have --no-blobs, --no-owner,
> --no-password, --no-privileges, --no-acl, --no-tablespaces, and
> --no-security-labels. It seems like there is probably a fairly large
> use case for excluding subscriptions even if you have sufficient
> permissions to dump them.
What purpose would that serve in practice? The subscriptions are now
dumped disabled, so if they hang around, there is not much impact.
Perhaps an option that also omits publications would make sense?
Or a general filtering facility based on the object tag?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2017-04-14 01:57:10 | Re: Logical replication and inheritance |
| Previous Message | Masahiko Sawada | 2017-04-14 01:47:46 | Re: Quorum commit for multiple synchronous replication. |