| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | fabriziomello(at)gmail(dot)com, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements |
| Date: | 2013-06-20 16:24:05 |
| Message-ID: | 51C32CA5.3020104@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/20/13 11:04 AM, Robert Haas wrote:
> I kind of don't see the point of having IF NOT EXISTS for things that
> have OR REPLACE, and am generally in favor of implementing OR REPLACE
> rather than IF NOT EXISTS where possible.
I tend to agree.
>> > Btw., I also want REPLACE BUT DO NOT CREATE.
> That's a mouthful. What's it good for?
If you run an upgrade SQL script that is supposed to replace, say, a
bunch of functions with new versions, you'd want the behavior that it
replaces the existing function if it exists, but errors out if it
doesn't, because then you're perhaps connected to the wrong database.
It's a marginal feature, and I'm not going to pursue it, but if someone
wanted to make the CREATE commands fully featured, there is use for this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-06-20 16:33:25 | Re: backend hangs at immediate shutdown (Re: Back-branch update releases coming in a couple weeks) |
| Previous Message | Andres Freund | 2013-06-20 15:45:26 | Re: dynamic background workers |