| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: alter enum add value if not exists |
| Date: | 2012-09-22 21:55:37 |
| Message-ID: | 505E33D9.5050704@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at)dunslane(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-22 22:00:59 | Re: alter enum add value if not exists |
| Previous Message | Andrew Dunstan | 2012-09-22 21:49:19 | Re: alter enum add value if not exists |