Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VGVSN-0003bl-9Y for pgsql-docs@arkaria.postgresql.org; Mon, 02 Sep 2013 14:50:19 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VGVSM-0003s7-OY for pgsql-docs@arkaria.postgresql.org; Mon, 02 Sep 2013 14:50:18 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VGVSL-0003qX-Cg for pgsql-docs@postgresql.org; Mon, 02 Sep 2013 14:50:17 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VGVSI-0001hi-L7 for pgsql-docs@postgresql.org; Mon, 02 Sep 2013 14:50:16 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id r82Eo9M2015352; Mon, 2 Sep 2013 10:50:09 -0400 From: Tom Lane To: Vik Fearing cc: PG Docs Subject: Re: VALIDATE CONSTRAINT In-reply-to: <52244B75.6040507@dalibo.com> References: <52244B75.6040507@dalibo.com> Comments: In-reply-to Vik Fearing message dated "Mon, 02 Sep 2013 10:25:25 +0200" Date: Mon, 02 Sep 2013 10:50:09 -0400 Message-ID: <15351.1378133409@sss.pgh.pa.us> X-Pg-Spam-Score: -2.4 (--) 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 Vik Fearing writes: > Is there a reason, besides simple oversight, that commit > 073d7cb513f5de44530f4bdbaaa4b5d4cce5f984 was not backpatched? > I think it needs to be. AFAICS, it was. Author: Simon Riggs Branch: master [073d7cb51] 2013-06-18 12:09:39 +0100 Branch: REL9_3_STABLE [0ae1bf8c1] 2013-06-18 12:10:10 +0100 Branch: REL9_2_STABLE [20a562f91] 2013-06-18 12:00:32 +0100 Branch: REL9_1_STABLE [be039d4b2] 2013-06-18 12:05:48 +0100 Fix docs on lock level for ALTER TABLE VALIDATE ALTER TABLE .. VALIDATE CONSTRAINT previously gave incorrect details about lock levels and therefore incomplete reasons to use the option. Initial bug report and fix from Marko Tiikkaja Reworded by me to include comments by Kevin Grittner regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs