Re: ALTER DATABASE vs pg_dump - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ALTER DATABASE vs pg_dump
Date
Msg-id 2586.1214578051@sss.pgh.pa.us
Whole thread Raw
In response to ALTER DATABASE vs pg_dump  (Richard Huxton <dev@archonet.com>)
Responses Re: ALTER DATABASE vs pg_dump
List pgsql-hackers
Richard Huxton <dev@archonet.com> writes:
> Is it desirable that pg_dump doesn't dump config settings set via ALTER 
> DATABASE?

Well, it's intentional anyway: that's handled by pg_dumpall.  The basic
design is that anything that can be seen from "outside" a specific
database is handled on the pg_dumpall side.

> I just got bitten by a DateStyle not being restored on my test DB

You could also get bitten by not having restored users or tablespaces
that the dump depends on, so I'm not sure there's a strong argument
here for refactoring the responsibility.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Michael Meskes
Date:
Subject: Re: ecpg generated files ignorable?
Next
From: Simon Riggs
Date:
Subject: Re: Hint Bits and Write I/O