Re: check constraint validation takes access exclusive locks

Excerpts from Pavel Stehule's message of lun feb 27 10:41:32 -0300 2012:
>
> 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.

Yeah :-(

> Is it final behave or will be fixed on 9.2?

It's final for 9.2 AFAIK. It's supposed to get fixed during the 9.3
timeframe.

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