Re: SUBSCRIPTIONS and pg_upgrade

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SUBSCRIPTIONS and pg_upgrade
Date: 2017-04-17 19:54:41
Message-ID: 20170417195441.GE9812@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter,

* Peter Eisentraut (peter(dot)eisentraut(at)2ndquadrant(dot)com) wrote:
> 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.

Will they be allowed to be created as a non-superuser when loading into
another cluster? Even if you might have superuser rights on one
cluster, you may not on another.

> Perhaps an option that also omits publications would make sense?

Yes.

> Or a general filtering facility based on the object tag?

Perhaps.. I'd hate for it to end up being overly complicated though.
The general '--no-security-lables', '--no-tablespaces' and other options
are pretty straight-forward and I think that's a good thing.

Thanks!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2017-04-17 20:09:28 Re: Self-signed certificate instructions
Previous Message Stephen Frost 2017-04-17 19:51:01 Re: Row Level Security UPDATE Confusion