Re: [HACKERS] problems with pg_restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
Cc: Rod Taylor <rbt(at)rbt(dot)ca>, "Kuhn, Dylan K (4520500D)" <Dylan(dot)Kuhn(at)navy(dot)mil>, pgsql-admin(at)postgresql(dot)org, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] problems with pg_restore
Date: 2003-07-16 14:41:39
Message-ID: 18172.1058366499@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> On Tue, Jul 15, 2003 at 04:03:13PM -0400, Tom Lane wrote:
>> Given the current implementation, it seems like there are three possible
>> behaviors for COMMENT ON DATABASE when the database name isn't the same
>> as the current database:

> There's a fourth possibility: ignore the command and issue a WARNING.

Hmm, that seems like a reasonable choice. Anyone have an objection?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andrew Biagioni 2003-07-16 22:37:52 Re: [HACKERS] problems with pg_restore
Previous Message Alvaro Herrera 2003-07-15 20:47:04 Re: [HACKERS] problems with pg_restore

Browse pgsql-hackers by date

  From Date Subject
Next Message scott.marlowe 2003-07-16 14:55:48 Re: Criteria for contrib/ versus gborg?
Previous Message Christoph Haller 2003-07-16 14:06:46 Re: FROM clause omitted