| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Vitaly Burovoy <vitaly(dot)burovoy(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: identity columns |
| Date: | 2017-04-03 20:27:42 |
| Message-ID: | 59d8e32a-14de-6f45-c2b0-bb52e4a7522d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/30/17 22:57, Vitaly Burovoy wrote:
> Why do you still want to leave "ADD IF NOT EXISTS" instead of using
> "SET IF NOT EXISTS"?
> If someone wants to follow the standard he can simply not to use "IF
> NOT EXISTS" at all. Without it error should be raised.
As I tried to mention earlier, it is very difficult to implement the IF
NOT EXISTS behavior here, because we need to run the commands the create
the sequence before we know whether we will need it. So this is a bit
different from many other ALTER TABLE commands. It could be done, but
it would require some major reworking of things or a new idea of some
kind. It could be done later, but I think it's not worth holding things
up for that.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-04-03 20:31:27 | Re: identity columns |
| Previous Message | Daniel Verite | 2017-04-03 20:26:24 | Re: Variable substitution in psql backtick expansion |