Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bmOvl-0006GG-8i for pgsql-docs@arkaria.postgresql.org; Tue, 20 Sep 2016 17:34:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bmOvk-0004gw-P2 for pgsql-docs@arkaria.postgresql.org; Tue, 20 Sep 2016 17:34:04 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bmOvk-0004gZ-4y for pgsql-docs@postgresql.org; Tue, 20 Sep 2016 17:34:04 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bmOvh-00031G-EN for pgsql-docs@postgresql.org; Tue, 20 Sep 2016 17:34:02 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 78D25205B9; Tue, 20 Sep 2016 13:34:00 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 20 Sep 2016 13:34:00 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=a5pKwAfKnze+SM4 Wxzg54AHJGn0=; b=ZxTmWLADJR1DNNzqGiRXgHMe0AvZh5GSYbj8hxrNpaPYeKH rhmUc/PF4U/0xnYbnw5Wczm4IS1bH7SQWkhm8IAXEGEaqtms9A1GHyU44ZnbZi20 0pzVmNKfC97ia658er3TXe2DyfXG7Sa4PmWnkx+TUhv5PgYWNvykY/0DrNF4= X-Sasl-enc: 7C6Vawe8AEgpIJCtiBh07kToVkabjsdrVA4MLz9zjSaj 1474392840 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 33AAECCE8B; Tue, 20 Sep 2016 13:34:00 -0400 (EDT) Subject: Re: Exclude constraints not shown ALTER TABLE documentation page To: onder@citusdata.com, pgsql-docs@postgresql.org References: <20160919134201.1348.87378@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <875a5b71-3ca6-b0c8-c3ba-585f0a2ddc38@2ndquadrant.com> Date: Tue, 20 Sep 2016 13:33:59 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <20160919134201.1348.87378@wrigleys.postgresql.org> 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-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 9/19/16 9:42 AM, onder@citusdata.com wrote: > Though it is possible to add EXCLUDE CONSTRAINTs via ALTER TABLE as appears > here > http://thoughts.davisjeff.com/2010/09/25/exclusion-constraints-are-generalized-sql-unique/ > we could not see it on the related doc here > https://www.postgresql.org/docs/9.5/static/sql-altertable.html The ALTER TABLE page does not mention any specific constraint types, instead referring to the CREATE TABLE page. So this is not an omission of exclude constraints, but an intentional way to reduce duplication. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs