Re: alter enum add value if not exists - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: alter enum add value if not exists
Date
Msg-id 505E33D9.5050704@2ndQuadrant.com
Whole thread Raw
In response to Re: alter enum add value if not exists  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: alter enum add value if not exists  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 09/22/2012 11:49 PM, Andrew Dunstan wrote:
>
> On 09/22/2012 05:39 PM, Tom Lane wrote:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> The enum piece is now committed.
>> BTW, looking at that a second time ... the other CREATE IF NOT EXISTS
>> options we have issue a NOTICE when skipping the CREATE action. Is
>> there a reason this shouldn't do the same?
>>
>>
>
> Not really, I guess we should for the sake of consistency, although TBH
> I find it just useless noise and rather wish we hadn't started the 
> trend when we did the first DROP IF NOT EXISTS stuff.
Time for a GUC

existence_notice = none | exists | not_exists | all

?

Cheers,
Hannu Krosing



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: alter enum add value if not exists
Next
From: Tom Lane
Date:
Subject: Re: alter enum add value if not exists