Re: SUBSCRIPTIONS and pg_upgrade

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(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-13 16:11:30
Message-ID: CA+Tgmoa7ZnfNq2zBO9og7DAQDe7+FctR7WggGx2tbLXYeXHBFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 13, 2017 at 12:05 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-04-13 16:13:30 Re: Cutting initdb's runtime (Perl question embedded)
Previous Message Robert Haas 2017-04-13 16:06:38 Re: pg_upgrade vs extension upgrades