Hello Tom,
thank You very much.
> We improved that situation in v11, I believe. What I see for this
> case these days is per commit 5955d9341:
> [...]
Ah, well. I don't fully understand that, but as the iessue appears to
be known, then that is fine with me.
This thing is just bad if one neve
Hi Adrian,
okay, lets check these out:
> What is ${daily_pgsql_user} equal to?
postgres. The owner of the installation.
> I am not seeing -U postgres.
> Are you sure there is not something else specifying the user e.g. env
> PGUSER?
I'm sure. The log shows the nightly backup connections as
po
Peter writes:
> If you do only "pg_restore -c -d ", the sessions can stay open,
> but then it will do
> DROP SCHEMA public;
> CREATE SCHEMA public;
> and it will NOT restore the grant because it is not in the backup.
We improved that situation in v11, I believe. What I see for this
case these da
Long story short:
pg_dump just forgets to backup the grant on schema public. :(
Long story:
After searching for half an hour to get some comprehensive listing
of permissions (which was in vain) I tried with pgadmin3 (which is
indeed a life-saver and still somehow works on 10.10 - and that's
t
On 11/6/19 11:11 AM, Peter wrote:
This is FreeBSD 11.3, with postgres installed from ports as 10.10.
There is included a daily utility doing pg_dump:
: ${daily_pgsql_pgdump_args:="-U ${daily_pgsql_user} -p ${daily_pgsql_port} -bF
c"}
pg_dump ${daily_pgsql_pgdump_args} -f ${file} ${db}
What
This is FreeBSD 11.3, with postgres installed from ports as 10.10.
There is included a daily utility doing pg_dump:
: ${daily_pgsql_pgdump_args:="-U ${daily_pgsql_user} -p ${daily_pgsql_port} -bF
c"}
pg_dump ${daily_pgsql_pgdump_args} -f ${file} ${db}
Recently I did a restore of some database
