| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| 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-19 19:27:15 |
| Message-ID: | 200711191927.lAJJRFF09412@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jose Tomas Eterovic | 2007-11-19 19:30:28 | BUG #3761: Problems with to_char(timestamp) and milliseconds |
| Previous Message | Alvaro Herrera | 2007-11-19 18:49:45 | Re: BUG #3760: Comment on restore database |