Message-ID: <51A89BAE.6000704@joh.to>
Date: Fri, 31 May 2013 14:46:38 +0200
From: Marko Tiikkaja <marko@joh.to>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
	rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: pgsql-docs@postgresql.org
Subject: Re: ALTER TABLE lock level
References: <51A37A72.5000203@joh.to>
In-Reply-To: <51A37A72.5000203@joh.to>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-docs-owner@postgresql.org

On 5/27/13 5:23 PM, I wrote:
> Today I got (unfortunately) reminded that this statement, in
> sql-altertable.html under VALIDATE CONSTRAINT, is not true anymore:
>
> The value of separating validation from initial creation of the
> constraint is that validation requires a lesser lock on the table than
> constraint creation does.

Since nobody seems to want to pick this up, I'm going to suggest the 
following wording:

    The value of separating validation from initial creation of the
    constraint is that you can immediately start enforcing the
    constraint on all future rows, but delay the validation of
    pre-existing data until your database is not under heavy load.

But I'm not going to object to simply removing the entire sentence.


Regards,
Marko Tiikkaja


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