Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements. - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements.
Date
Msg-id AANLkTikfO6vgB-Jfvmt_cWGktiwYFFXEhgAQMVf8Hbg_@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements.  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements.  (Peter Eisentraut <peter_e@gmx.net>)
Re: [PATCH] Return command tag 'REPLACE X' for CREATE OR REPLACE statements.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Mon, Jan 17, 2011 at 9:41 AM, Peter Eisentraut <peter_e@gmx.net> wrote:
> On fre, 2011-01-14 at 18:45 -0500, Robert Haas wrote:
>> On Fri, Jan 14, 2011 at 3:45 PM, Marti Raudsepp <marti@juffo.org>
>> wrote:
>> > There's a similar case with CREATE TABLE IF NOT EXISTS, maybe this
>> is
>> > worth covering in an updated patch too?
>> > And if I change that, people might expect the same from DROP X IF
>> EXISTS too?
>>
>> It's far less clear what you'd change those cases to say, and they
>> already emit a NOTICE, so it seems unnecessary.
>
> Maybe instead of the proposed patch, a notice could be added:
>
> NOTICE: existing object was replaced

Well, that would eliminate the backward-compatibility hazard, pretty
much, but it seems noisy.  I already find some of these notices to be
unduly informative.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: SSI patch version 12
Next
From: Magnus Hagander
Date:
Subject: Re: Replication logging