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

Re: BUG #3760: Comment on restore database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(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:14:01
Message-ID: 8655.1195517641@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
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.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2007-11-20 00:18:54
Subject: Re: BUG #3760: Comment on restore database
Previous:From: Bruce MomjianDate: 2007-11-19 23:47:06
Subject: Re: BUG #3760: Comment on restore database

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