On Mon, 2007-11-19 at 14:27 -0500, Bruce Momjian wrote:
> 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.
Can we implement something for 8.3 please?
Suggested syntax even simpler
COMMENT ON DATABASE IS 'text';
to set the comment on the current database.
Reason to do this now: Perf Tips have been changed for 8.3 to recommend
using --single-transaction when restoring pg_dumps, because of fast COPY
enhancement. Allowing this to cause an error will prevent the whole dump
from restoring. That will force people to find the cause of the error,
for which there is no hint, edit the file and resubmit.
Fairly simple to allow working syntax, and useful too.
In response to
pgsql-bugs by date
|Next:||From: Bruce Momjian||Date: 2007-11-19 21:29:47|
|Subject: Re: [BUGS] BUG #3761: Problems with to_char(timestamp) and
|Previous:||From: Hussain Jawad-FXRM43||Date: 2007-11-19 19:47:48|
|Subject: Re: Start up error |