Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> This is an extremely poorly phrased TODO item. > > > OK, updated: > > > o Prevent COMMENT ON dbname from issuing a warning when loading > > into a database with a different name, perhaps using COMMENT ON > > CURRENT DATABASE > > That's not any better, because the warning isn't the problem either. > Perhaps: > > o Change pg_dump so that any comment on the dumped database is > applied to the database the dump is loaded into, even if > its database name is different. This will require new > backend syntax, perhaps COMMENT ON CURRENT DATABASE.
Thanks, done: > o Change pg_dump so that a comment on the dumped database is > applied to the loaded database, even if the database has a > different name. This will require new backend syntax, perhaps > COMMENT ON CURRENT DATABASE. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
