From: Alvaro Herrera <alvherre@dcc.uchile.cl>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Rod Taylor <rbt@rbt.ca>
Cc: Kuhn, Dylan K (4520500D) <Dylan.Kuhn@navy.mil>
Cc: pgsql-admin@postgresql.org, PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] problems with pg_restore
Date: Tue, 15 Jul 2003 16:47:04 -0400
Message-ID: <20030715204704.GC9410@dcc.uchile.cl> (raw)
In-Reply-To: <8299.1058299393@sss.pgh.pa.us>
References: <78ED1F30F0D85B4698FBD6CF2A5AC8F5A576F9@NAWECHLKEX01VA.nadsuswe.nads.navy.mil>
<23211.1058286389@sss.pgh.pa.us>
<1058298650.9981.117.camel@jester>
<8299.1058299393@sss.pgh.pa.us>
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)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@dcc.uchile.cl, tgl@sss.pgh.pa.us, rbt@rbt.ca, Dylan.Kuhn@navy.mil, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] problems with pg_restore
In-Reply-To: <20030715204704.GC9410@dcc.uchile.cl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox