From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | joe(at)tanga(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #7874: GUC's not in database dumps |
Date: | 2013-02-15 20:33:47 |
Message-ID: | 20130215203347.GD12030@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Feb 14, 2013 at 01:37:04AM +0000, joe(at)tanga(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7874
> Logged by: Joe Van Dyk
> Email address: joe(at)tanga(dot)com
> PostgreSQL version: 9.2.1
> Operating system: OSX, Linux
> Description:
>
> If I run:
> alter database foo set my.name = 'joe';
>
> that GUC isn't available inside backups of that database.
>
> It does show up when doing "pg_dumpall -s".
>
> It does *not* show up when doing "pg_dumpall -g"
>
This is a TODO:
https://wiki.postgresql.org/wiki/Todo#ALTER
Refactor handling of database attributes between pg_dump and pg_dumpall
Currently only pg_dumpall emits database attributes, such as ALTER
DATABASE SET commands and database-level GRANTs. Many people wish that
pg_dump would do that. One proposal is to let pg_dump issue such
commands if the -C switch was used, but it's unclear whether that will
satisfy the demand.
http://www.postgresql.org/message-id/4864F001.50909@archonet.com
http://www.postgresql.org/message-id/11646.1272814212@sss.pgh.pa.us
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-02-15 20:42:29 | Re: BUG #7885: postmaster panic on startup does not release shared memory |
Previous Message | Bruce Momjian | 2013-02-15 20:32:05 | Re: BUG #7873: pg_restore --clean tries to drop tables that don't exist |