Re: [ADMIN] problems with pg_restore - Mailing list pgsql-hackers

From Andrew Biagioni
Subject Re: [ADMIN] problems with pg_restore
Date
Msg-id 3F15D3C0.4060707@e-greek.net
Whole thread Raw
In response to Re: [ADMIN] problems with pg_restore  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
Alvaro Herrera <alvherre@dcc.uchile.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?

My personal experience would lead me to believe that this is the best option.  Count it a vote in favor.
			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
              http://archives.postgresql.org

        Andrew Biagioni

pgsql-hackers by date:

Previous
From: marcus.boerger@t-online.de (Marcus Börger)
Date:
Subject: Re: php with postgres
Next
From: marcus.boerger@t-online.de (Marcus Börger)
Date:
Subject: Re: php with postgres