From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vik Fearing <vik.fearing@dalibo.com>
Cc: PG Docs <pgsql-docs@postgresql.org>
Subject: Re: VALIDATE CONSTRAINT
Date: Mon, 02 Sep 2013 10:50:09 -0400
Message-ID: <15351.1378133409@sss.pgh.pa.us> (raw)
In-Reply-To: <52244B75.6040507@dalibo.com>
References: <52244B75.6040507@dalibo.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-docs>
Vik Fearing <vik.fearing@dalibo.com> 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 <simon@2ndQuadrant.com>
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
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-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, vik.fearing@dalibo.com
Subject: Re: VALIDATE CONSTRAINT
In-Reply-To: <15351.1378133409@sss.pgh.pa.us>
* 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