| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SUBSCRIPTIONS and pg_upgrade |
| Date: | 2017-02-17 14:13:33 |
| Message-ID: | 14800830-6026-ce2b-1eb6-c4ad3d256229@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/16/17 21:04, Stephen Frost wrote:
> I'm not entirely sure about the reasoning behind requiring a flag to
> include subscriptions in pg_dump output,
One reason is that pg_subscription is only readable by a superuser, so
we can't even dump them unless we're superuser.
Also, restoring a subscription will immediately attempt to start
replication, which might be kind of surprising.
We had pondered this issue extensively during early review. I don't
think we're all happy with the current behavior, but it's probably the
safest and easiest one for now.
Better ideas are welcome.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-02-17 14:14:50 | Re: CREATE SUBSCRIPTION uninterruptable |
| Previous Message | Michael Paquier | 2017-02-17 14:05:31 | Re: REINDEX CONCURRENTLY 2.0 |