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:
I`m sorry, but why work around?
The overhead of "99%" of cases is so bigger? What about an "option"
like constraint exclusion...
I've worked around also, but would like to see this topic in a TODO or
further implementation.
Thanks by patience.
Kevin Grittner escreveu:
ork as the same as "=" operator.
But, if it is not a BUG, i'm so sorry!
Best Regards,
Tiago
Tom Lane escreveu:
Alvaro Herrera <[EMAIL PROTECTED]> writes:
Tiago Daniel Jacobs wrote:
"-> Index Scan using idx_agreg_sig_2007_09__data
The following bug has been logged online:
Bug reference: 3657
Logged by: Tiago Daniel Jacobs
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: Linux
Description:Performance leaks when using between of two equal dates
Details:
Hi, please
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
