Tom, all,
* Tom Lane (t...@sss.pgh.pa.us) wrote:
> =?iso-8859-1?Q?Bo_Thorbj=F8rn_Jensen?= writes:
> > I have some additional info and a fix.
> > Firstly steps to reproduce:
>
> Yeah, I can reproduce this. I suspect it got broken by Stephen's hacking
> around with default
=?iso-8859-1?Q?Bo_Thorbj=F8rn_Jensen?= writes:
> I have some additional info and a fix.
> Firstly steps to reproduce:
Yeah, I can reproduce this. I suspect it got broken by Stephen's hacking
around with default ACLs. A simple example is
$ pg_dump -c -U postgres postgres |
I have some additional info and a fix.
Firstly steps to reproduce:
1. create database:
CREATE DATABASE test WITH ENCODING='UTF8' OWNER=postgres CONNECTION LIMIT=-1;
-- here public has access to public
2. dump:
pg_dump -f testfile.dump -F c -h localhost -U postgres test
3. restore:
pg_restore
Hi
We recently upgraded from 9.1 to 9.6 (now 9.6.6) and have, after dump/restore
on 9.6, experienced the loss of public priviliges on schema public.
Is this a "feature" or some kind of bug ?
I have found a thread here that looks sortof similar with subject: "[GENERAL]
intentional or