Hi, why if I REINDEX a inherited table, all tables are locked?
Example:
[conn #1] REINDEX TABLE month_a;
[conn #2] PREPARE updt as update month_b set col_a=1 where col_b=$1;
The query on conn#2 waits.
regards,
Tiago
Tom Lane escreveu:
"Tiago Jacobs" <[EMAIL PROTECTED]> writes:
On Mon, 2007-07-23 at 11:46 -0300, Tiago Daniel Jacobs wrote:
> Tom and Gregory. U're right! The problem is that we're using
> constraints for partitioned tables and by definition, a partition
> never, absolutely never, can affect the entire system.
>
Yeh, the problem is that partitioning uses ad
"Tiago Daniel Jacobs" <[EMAIL PROTECTED]> writes:
> Tom and Gregory. U're right! The problem is
> that we're using constraints for partitioned tables and by definition,
> a partition never, absolutely never, can affect the entire system.
>
> But I think that we have nothing to do about this. Th
Tom and Gregory. U're right! The problem is
that we're using constraints for partitioned tables and by definition,
a partition never, absolutely never, can affect the entire system.
But I think that we have nothing to do about this. There are plans to
another kind of partitioning? If yes, I w
"Tiago Jacobs" <[EMAIL PROTECTED]> writes:
> oh-ow... It waits while the table (That is not used) is locked.
This is not a bug. It has to inspect the table to find out that
there is a constraint.
regards, tom lane
---(end of broadcast)
"Tiago Jacobs" <[EMAIL PROTECTED]> writes:
> oh-ow... It waits while the table (That is not used) is locked.
>
> Even that the final plan dont use tab_2007_07, it wait for unlock of table
> for make the plan.
Well one of the reasons exclusive locks are taken are to make changes to
constraints.
>
The following bug has been logged online:
Bug reference: 3479
Logged by: Tiago Jacobs
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux 2.6.21.5
Description:contraint exclusion and locks
Details:
Hi People!
Connection #1
create tabl
