Re: [HACKERS] Addition of pg_dump --no-publications - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Addition of pg_dump --no-publications
Date
Msg-id CAB7nPqTHWEyKkvrhU1DkP5FNfL7uC4XSn_e=Vnatq4o7od6j9A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Addition of pg_dump --no-publications  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Fri, May 12, 2017 at 10:19 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 5/11/17 21:59, Michael Paquier wrote:
>> On Thu, May 11, 2017 at 3:19 PM, Michael Paquier
>> <michael.paquier@gmail.com> wrote:
>>> I imagine that pg_dump -s would be the basic operation that users
>>> would do first before creating a subcription on a secondary node, but
>>> what I find surprising is that publications are dumped by default. I
>>> don't find confusing that those are actually included by default to be
>>> consistent with the way subcriptions are handled, what I find
>>> confusing is that there are no options to not dump them, and no
>>> options to bypass their restore.
>>>
>>> So, any opinions about having pg_dump/pg_restore --no-publications?
>>
>> And that's really a boring patch, giving the attached.
>
> committed

Thanks.
-- 
Michael



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] multi-column range partition constraint
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Hash Functions