Re: [HACKERS] problems with pg_restore

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-15 20:47:04
Message-ID: 20030715204704.GC9410@dcc.uchile.cl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

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.
Restores the database in both cases (in same database and in a different
one), and sets the correct comment only if the database name is correct,
giving a hint that the comment should be manually set.

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"I can't go to a restaurant and order food because I keep looking at the
fonts on the menu. Five minutes later I realize that it's also talking
about food" (Donald Knuth)

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2003-07-16 14:41:39 Re: [HACKERS] problems with pg_restore
Previous Message Rod Taylor 2003-07-15 20:30:59 Re: problems with pg_restore

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-07-15 21:14:52 Re: OSF build fixed
Previous Message Kurt Roeckx 2003-07-15 20:39:58 Re: OSF build fixed