X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.225.181]) by svr1.postgresql.org (Postfix) with ESMTP id 0F2BACC78B; Wed, 16 Jul 2003 22:38:10 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr5.postgresql.org [64.117.225.181]) (amavisd-new, port 10024) with ESMTP id 14475-04; Wed, 16 Jul 2003 22:38:24 +0000 (GMT) Received: from proteus.affordablehost.com (proteus.affordablehost.com [216.46.203.177]) by svr1.postgresql.org (Postfix) with ESMTP id 732C7CC7C4; Wed, 16 Jul 2003 19:37:58 -0300 (ADT) Received: from [66.92.74.181] (helo=e-greek.net) by proteus.affordablehost.com with esmtp (Exim 4.20) id 19cuuF-0005JS-4Y; Wed, 16 Jul 2003 18:37:51 -0400 Message-ID: <3F15D3C0.4060707@e-greek.net> Date: Wed, 16 Jul 2003 18:37:52 -0400 From: Andrew Biagioni User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Alvaro Herrera , Rod Taylor , "Kuhn, Dylan K (4520500D)" , pgsql-admin@postgresql.org, PostgreSQL Development Subject: Re: [HACKERS] problems with pg_restore References: <78ED1F30F0D85B4698FBD6CF2A5AC8F5A576F9@NAWECHLKEX01VA.nadsuswe.nads.navy.mil> <23211.1058286389@sss.pgh.pa.us> <1058298650.9981.117.camel@jester> <8299.1058299393@sss.pgh.pa.us> <20030715204704.GC9410@dcc.uchile.cl> <18172.1058366499@sss.pgh.pa.us> In-Reply-To: <18172.1058366499@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------020801000605030407020604" X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/142 X-Sequence-Number: 9482 This is a multi-part message in MIME format. --------------020801000605030407020604 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Tom Lane wrote: >Alvaro Herrera 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 --------------020801000605030407020604 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 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

--------------020801000605030407020604--