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 200711191927.lAJJRFF09412@momjian.us
Whole thread Raw
In response to Re: BUG #3760: Comment on restore database  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: BUG #3760: Comment on restore database
List pgsql-bugs
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Malcus Imhof wrote:
>
> > Yea, the dump thinks it is going into the same database.  I don't see
> > any way of fixing that.  We don't allow functions for the object name.
> > If we did we could use current_database().  Fortunately I think it is
> > the only place where the database name is hardcoded in the dump.
>
> The easiest would be to add new syntax,
> COMMENT ON CURRENT DATABASE IS 'foo'

Yea, probably.  I have added that as possible syntax to the TODO list.

--
  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: Alvaro Herrera
Date:
Subject: Re: BUG #3760: Comment on restore database
Next
From: "Jose Tomas Eterovic"
Date:
Subject: BUG #3761: Problems with to_char(timestamp) and milliseconds