On Thu, Apr 13, 2017 at 12:05 PM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > On 4/12/17 18:31, Peter Eisentraut wrote: >> On 4/11/17 23:41, Noah Misch wrote: >>> On Tue, Apr 11, 2017 at 11:21:24PM -0400, Peter Eisentraut wrote: >>>> On 4/9/17 22:16, Noah Misch wrote: >>>>> [Action required within three days. This is a generic notification.] >>>> >>>> Patches have been posted. Discussion is still going on a bit. >>> >>> By what day should the community look for your next update? >> >> tomorrow > > Everything has been committed, and this thread can be closed.
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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
