From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | fujimoto(at)ceptord(dot)net, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14788: `pg_restore -c` won't restore schema access privileges. |
Date: | 2017-08-24 14:26:05 |
Message-ID: | 20170824142605.GD4628@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> fujimoto(at)ceptord(dot)net writes:
> > [ dump to archive, then pg_restore with -c option ]
>
> > Now all the access privileges on the public schema are gone:
>
> I can confirm this is broken in HEAD: "pg_dump -c test >test.out"
> produces a script including "GRANT ALL ON SCHEMA public TO PUBLIC",
> but "pg_dump -Fc test >test.dump; pg_restore -c test.dump" produces
> a script lacking that.
Ugh.
> Stephen attempted to fix this in 330b84d8c, but the fix was evidently done
> incorrectly. There should never be any difference between the results of
> these two procedures. I've not studied 330b84d8c, but my strong suspicion
> is that the logic was added to the wrong place in pg_dump.
I'm afraid it's not quite that simple, unfortunately.
I'll see what I can do though. I'm really curious how this was working
previously..
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2017-08-24 14:49:33 | Re: BUG #14788: `pg_restore -c` won't restore schema access privileges. |
Previous Message | Tom Lane | 2017-08-24 14:18:35 | Re: BUG #14788: `pg_restore -c` won't restore schema access privileges. |