Skip site navigation (1) Skip section navigation (2)

Re: check constraint validation takes access exclusive locks

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: depesz <depesz(at)depesz(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: check constraint validation takes access exclusive locks
Date: 2012-02-27 13:41:32
Message-ID: CAFj8pRDUcBttDCeSYpq2Ck2eZN0OXS+L7RGYTys7vkrd8wyZ3Q@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2012/2/27 Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
>
> Excerpts from hubert depesz lubaczewski's message of lun feb 27 10:02:57 -0300 2012:
>> On Sun, Feb 26, 2012 at 03:04:28PM +0100, Pavel Stehule wrote:
>> > Hello
>> >
>> > I rechecked Depesz's article -
>> > http://www.depesz.com/2011/07/01/waiting-for-9-2-not-valid-checks/
>> >
>> > The behave of current HEAD is different than behave described in article.
>> >
>> > "alter table a validate constraint a_a_check" needs a access exclusive
>> > locks and blocks table modification - I tested inserts.
>
>> yes, looks like we have revert to access exclusive lock:
>
> See commits
> 2c3d9db56d5d49bdc777b174982251c01348e3d8
> and
> a195e3c34f1eeb6a607c342121edf48e49067ea9

 this block a sense of NOT VALIDATE constraints. Is it final behave or
will be fixed on 9.2?

Regards

Pavel



>
> --
> Álvaro Herrera <alvherre(at)commandprompt(dot)com>
> The PostgreSQL Company - Command Prompt, Inc.
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2012-02-27 13:52:33
Subject: Re: check constraint validation takes access exclusive locks
Previous:From: Robert HaasDate: 2012-02-27 13:36:09
Subject: Re: pgstat documentation tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group