On Friday 27 June 2008 12:58:41 Richard Huxton wrote: > Richard Huxton wrote: > > Richard Huxton wrote: > >> At present it means you can't reliably do: > >> DROP DATABASE foo; > >> pg_restore --create foo.dump > >> I'd then have to either hand edit the dumpall dump or wade through a > >> bunch of errors checking that none of them were relevant. > > > > Actually, I'm not sure pg_dumpall does them either. > > [snip] > > > Am I doing something stupid here? > > OK - so to get the ALTER DATABASE commands I need to dump the schema for > the entire cluster. Is that really desired behaviour? >
Certainly not desired by a number of people I have talked to, but I don't have much hope in seeing the behavoir change... perhaps someday if we get around to merging pg_dump and pg_dumpall.... -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers