From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PUBLICATIONS and pg_dump |
Date: | 2017-02-08 04:02:40 |
Message-ID: | CAOuzzgrU5jyKT2XoFyui4uFXZX-SPDg3PB=aLEqX84Zf3QgWDg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Peter,
On Tue, Feb 7, 2017 at 22:49 Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> 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.
Great! I've added it to the open items list for PG10.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-02-08 20:55:58 | pgsql: Add WAL consistency checking facility. |
Previous Message | Peter Eisentraut | 2017-02-08 03:49:28 | Re: PUBLICATIONS and pg_dump |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-02-08 04:08:25 | drop support for Python 2.3 |
Previous Message | Peter Eisentraut | 2017-02-08 03:49:28 | Re: PUBLICATIONS and pg_dump |