pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Vitaly Burovoy <vitaly.burovoy@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: identity columns
Date: Mon, 3 Apr 2017 16:27:42 -0400
Message-ID: <59d8e32a-14de-6f45-c2b0-bb52e4a7522d@2ndquadrant.com> (raw)
In-Reply-To: <CAKOSWNnxgYCVoNbmr2reMvwzQzyzgXMZn8F5JQhvkdFs73ae2g@mail.gmail.com>
References: <6adbacbf-73bc-dd1a-2033-63409180fd18@2ndquadrant.com>
	<4ef801f2-64ce-1a58-277d-d9389ae7770d@2ndquadrant.com>
	<e287f723-d095-0d24-483a-3b7e3611c3e9@2ndquadrant.com>
	<CAKOSWNmsci7jZzpoqWAH_QcVjQzwOMf04o91Jf5WVTkHbDMy2w@mail.gmail.com>
	<1cf308b6-4f5c-05ba-cc74-0a7121603fcf@2ndquadrant.com>
	<CAKOSWNmKbthEdV0m1J=V7r6nDyPk8diKwHW93jYbB+wnXd-c1A@mail.gmail.com>
	<ed41b243-63b2-f287-e7b0-8b2ac7266d66@2ndquadrant.com>
	<CAKOSWNnMp0sKZzcX0zSKJOTSb1Fas02+xTW=kvGMu2NhRiOAbg@mail.gmail.com>
	<ec772da8-3443-b39d-e25e-138ef01a71c1@2ndquadrant.com>
	<CAKOSWNnXmM6YBXNzGnXtZQMPjDgJF+a3Wx53Wzmrq5wqDyRX7Q@mail.gmail.com>
	<c05eefac-0b55-74df-6343-71d232c15bc5@2ndquadrant.com>
	<CAKOSWNmRm0ydv1Yp8OzZ_GPh6Kfyhk+o-fxRb6onGfp433afFA@mail.gmail.com>
	<06a416db-e35b-36d1-7e2f-0affdee24745@2ndquadrant.com>
	<CAKOSWN=U0wfqjPuUbSEMAn_dcP7QnD_U0KskYf7OVhkVqs8CXA@mail.gmail.com>
	<4b1d703f-818f-00bf-4169-3279af377f3d@2ndquadrant.com>
	<CAKOSWNnxgYCVoNbmr2reMvwzQzyzgXMZn8F5JQhvkdFs73ae2g@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (55+ messages)  latest in thread

Message-ID: <59d8e32a-14de-6f45-c2b0-bb52e4a7522d@2ndquadrant.com>
Permalink:  ../59d8e32a-14de-6f45-c2b0-bb52e4a7522d@2ndquadrant.com/
Also on:    postgresql.org/message-id/59d8e32a-14de-6f45-c2b0-bb52e4a7522d@2ndquadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, vitaly.burovoy@gmail.com
  Subject: Re: identity columns
  In-Reply-To: <59d8e32a-14de-6f45-c2b0-bb52e4a7522d@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox