From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-14 01:47:12 |
Message-ID: | f7f54f75-14e5-8f04-7092-818281a07cf6@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13/04/17 18:11, Robert Haas wrote:
> 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.
>
+1, I'll look into writing patch for that
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2017-04-14 01:47:46 | Re: Quorum commit for multiple synchronous replication. |
Previous Message | Amit Langote | 2017-04-14 01:31:20 | Re: Declarative partitioning vs. information_schema |