Hi everybody.
I'm having an issues with wrong plan for query in PostgreSQL (version
8.3). EXPLAIN ANALYZE shows that there're a lot of places where
planner estimates row count totally wrong, like 1 instead of 12000+.
default_statistics_target variable is set to 100, and I tried to run
Hi, Andy,
Impact of other VMs is reflected as %steal time. And it's only this
specific UPDATE query on this specific table that ever exhibits the problem,
as measured over many days, a query that must represent something like 2%
of all queries run against the DB over the same period and 5%
Craig,
Thank you for the detailed reply. Thanks for walking me through the
thought process. Also thanks for serendipitous irqbalance suggestion.
Cheers
On Sep 17, 1:00 am, cr...@postnewspapers.com.au (Craig Ringer) wrote:
On Mon, 2009-09-14 at 14:48 -0700, C Storm wrote:
In this linux mag
Hi everybody.
I'm having an issues with wrong plan for query in PostgreSQL (version
8.3). EXPLAIN ANALYZE shows that there're a lot of places where
planner estimates row count totally wrong, like 1 instead of 12000+.
default_statistics_target variable is set to 100, and I tried to run
Hello,
I am trying to index a field in my database of size about 16K rows, but i m
getting this error.
Index row requires 9324 bytes maximum size is 8191
Can anyone please guide me how to remove this error
Also, average time to search for a query in a table is taking about 15
seconds.
solAris23 escreveu:
I am trying to index a field in my database of size about 16K rows, but i m
getting this error.
Why are you want to index such a big field? BTW, it'll be worthless.
Index row requires 9324 bytes maximum size is 8191
That is a known limitation; but even if it would be
Hello
2009/9/18 solAris23 vikas.ku...@dolcera.com:
Hello,
I am trying to index a field in my database of size about 16K rows, but i m
getting this error.
Index row requires 9324 bytes maximum size is 8191
Can anyone please guide me how to remove this error
Also, average time to
