Skip site navigation (1) Skip section navigation (2)

Re: Dumping datconfig

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Richard Huxton <dev(at)archonet(dot)com>
Subject: Re: Dumping datconfig
Date: 2008-07-31 15:09:39
Message-ID: 4891D5B3.6090809@hagander.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Magnus Hagander wrote:
> It seems the only way to dump stuff in pg_database.datconfig ("ALTER
> DATABASE foo SET something=bar") is to do an unqualified pg_dumpall.
> 
> I think this should *at least* be dumped with pg_dump when it's set to
> create the database, and I think a case could be made that it should
> *always* be dumped when a complete database is dumped by pg_dump (not
> restricted by schema or table or function or whatever).
> 
> Comments?
> 
> (I'll await the result of the discussion that's sure to happen before I
> write up a patch for it, but I'm willing to do said patch once agreement
> has been reached)

Hm. Ok, it seems I suck, and this discussion happened just over a month
ago at http://archives.postgresql.org/pgsql-hackers/2008-06/msg01035.php.

I agree with Richard that the behavior is not very nice though :-)

And I think
http://archives.postgresql.org/pgsql-hackers/2008-06/msg01142.php would
be the simplest way to fix it.


If there are no further comments, I'll crawl back under and try to work
up a complete proposal incl. code :-)

/Magnus

In response to

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2008-07-31 16:05:16
Subject: Re: [PATCHES] odd output in restore mode
Previous:From: Magnus HaganderDate: 2008-07-31 14:58:59
Subject: Re: Plans for 8.4

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group