Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cv8Zo-0007Ii-Mj for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Apr 2017 20:27:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cv8Zn-0004CB-NC for pgsql-hackers@arkaria.postgresql.org; Mon, 03 Apr 2017 20:27:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cv8Zn-0004AD-4U for pgsql-hackers@postgresql.org; Mon, 03 Apr 2017 20:27:47 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cv8Zk-0008PI-Jv for pgsql-hackers@postgresql.org; Mon, 03 Apr 2017 20:27:46 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2086420A4D; Mon, 3 Apr 2017 16:27:43 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Mon, 03 Apr 2017 16:27:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=69CE0wHLTlXOplsgvg92de3NWJiLxsbxN2uJx6Bj22E=; b=kJ6jFDfy +pru4bzBQb0GPsQmau2qqnEyElS5RObUS2IDLJx3uI01VX4HxT+MhcNB55lKT+7P mafyeiqZL5dJZLONpd4a/rIA4oVczvT7LE1dE5REOM9OE1pEzfw5SxYT0hEqXnv+ 0pivj9ogO2eZx+ruE5eJ4oxlcNCujoODFJrmsfsS3EsuA8B4clz8t9p9kGXfRA4v +omd5EVsxPPicmE5n+8LKBhjN+yoiXSaSd2FSm4x/g+cWs/XrRo4ZHcP9SswFU+e 9sFAnF/dcb9NrJcbdbd8XomUFRqMG+2DP5ujx8CLfiZ8L/0pb6AI6kHm753DOLZs IYZGKvs33X2W+A== X-ME-Sender: X-Sasl-enc: 9i8mOP0qEqvTLlM8kXI8Ptszl+QNqvWZ7oLPlpbCj8rJ 1491251262 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id CDBEB7E168; Mon, 3 Apr 2017 16:27:42 -0400 (EDT) Subject: Re: identity columns To: Vitaly Burovoy References: <6adbacbf-73bc-dd1a-2033-63409180fd18@2ndquadrant.com> <4ef801f2-64ce-1a58-277d-d9389ae7770d@2ndquadrant.com> <1cf308b6-4f5c-05ba-cc74-0a7121603fcf@2ndquadrant.com> <06a416db-e35b-36d1-7e2f-0affdee24745@2ndquadrant.com> <4b1d703f-818f-00bf-4169-3279af377f3d@2ndquadrant.com> Cc: pgsql-hackers From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <59d8e32a-14de-6f45-c2b0-bb52e4a7522d@2ndquadrant.com> Date: Mon, 3 Apr 2017 16:27:42 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org 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