Horton
Menu

Re: alter enum add value if not exists

Hannu Krosing <hannu@2ndquadrant.com>

View thread
From: Hannu Krosing <hannu@2ndQuadrant.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-09-22T21:55:37Z
Lists: 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