pg_db_role_setting info not dumped

Started by Adrian Klaverabout 15 years ago3 messagesgeneral
Jump to latest
#1Adrian Klaver
adrian.klaver@aklaver.com

Postgres 9.0.2
I used the ALTER DATABASE command to create a database specific SET
configuration. The problem is that information does not seem to be dumped. I
have tried pg_dumpall -g, pg_dumpall as well as a pg_dump for the individual
database. Am I missing something?
--
Adrian Klaver
adrian.klaver@gmail.com

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Adrian Klaver (#1)
Re: pg_db_role_setting info not dumped

Adrian Klaver <adrian.klaver@gmail.com> writes:

Postgres 9.0.2
I used the ALTER DATABASE command to create a database specific SET
configuration. The problem is that information does not seem to be dumped. I
have tried pg_dumpall -g, pg_dumpall as well as a pg_dump for the individual
database. Am I missing something?

Should be dumped by pg_dumpall (without the -g option).

There has been debate about whether plain pg_dump should deal with such
things, but nothing's been changed yet.

regards, tom lane

#3Adrian Klaver
adrian.klaver@aklaver.com
In reply to: Tom Lane (#2)
Re: pg_db_role_setting info not dumped

On Friday 14 January 2011 2:52:18 pm Tom Lane wrote:

Adrian Klaver <adrian.klaver@gmail.com> writes:

Postgres 9.0.2
I used the ALTER DATABASE command to create a database specific SET
configuration. The problem is that information does not seem to be
dumped. I have tried pg_dumpall -g, pg_dumpall as well as a pg_dump for
the individual database. Am I missing something?

Should be dumped by pg_dumpall (without the -g option).

There has been debate about whether plain pg_dump should deal with such
things, but nothing's been changed yet.

regards, tom lane

pg_dumpall worked. I missed it on my previous look. I vote for having it
included in the plain pg_dump output.

--
Adrian Klaver
adrian.klaver@gmail.com