Re: PUBLICATIONS and pg_dump

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: PUBLICATIONS and pg_dump
Date: 2017-02-08 03:49:28
Message-ID: 9314263d-f331-3ef0-a127-0c475f133914@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 2/7/17 3:19 PM, Stephen Frost wrote:
> I understand that this is a bit complicated, but I would have thought
> we'd do something similar to what is done for DEFAULT PRIVILEGES, where
> we include the "global" default privileges when we are doing a dump of
> "everything", but if we're dumping a specific schema then we only
> include the default privileges directly associated with that schema.
>
> Perhaps we need to include publications which are specific to a
> particular table, but the current logic of, essentially, "always include
> all publications" does not seem to make a lot of sense to me.

I think it would be sensible to refine it along those lines.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2017-02-08 04:02:40 Re: PUBLICATIONS and pg_dump
Previous Message Peter Eisentraut 2017-02-08 03:19:46 pgsql: Fix relcache leaks in get_object_address_publication_rel()

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-02-08 04:02:40 Re: PUBLICATIONS and pg_dump
Previous Message Merlin Moncure 2017-02-08 02:50:06 Re: Idea on how to simplify comparing two sets