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

Re: BUG #3760: Comment on restore database

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Malcus Imhof <malcus(at)terra(dot)com(dot)br>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3760: Comment on restore database
Date: 2007-11-20 00:18:54
Message-ID: 200711200018.lAK0Isd16431@momjian.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)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(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

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

In response to

pgsql-bugs by date

Next:From: CstdenisDate: 2007-11-20 07:57:27
Subject: BUG #3762: Inherited serials change on dump/restore
Previous:From: Tom LaneDate: 2007-11-20 00:14:01
Subject: Re: BUG #3760: Comment on restore database

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