Re: BUG #3760: Comment on restore database - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #3760: Comment on restore database
Date
Msg-id 200711200018.lAK0Isd16431@momjian.us
Whole thread Raw
In response to Re: BUG #3760: Comment on restore database  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> 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  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #3760: Comment on restore database
Next
From: Simon Riggs
Date:
Subject: Re: BUG #3760: Comment on restore database