Re: [GENERAL] Curious index selection when using a date range

2010-01-03 Thread Tom Lane
Scott Marlowe writes: > You might need to crank up the aggresiveness of auto-analyze, at least > on that one table if not for the whole db. This might be the same type of scenario Josh was complaining about: http://archives.postgresql.org/pgsql-hackers/2009-12/msg02308.php Inequality conditions n

Re: [GENERAL] Curious index selection when using a date range

2010-01-03 Thread Scott Marlowe
On Sun, Jan 3, 2010 at 2:16 PM, Robert Gravsjö wrote: > Scott Marlowe skrev 2010-01-03 22.03: >> On Sun, Jan 3, 2010 at 1:10 PM, Robert Gravsjö  wrote: >>> >>> I encountered a curious thing today. Simple select queries against a >>> fairly >>> large, ~60M rows, and active, both in reading and writ

Re: [GENERAL] Curious index selection when using a date range

2010-01-03 Thread Robert Gravsjö
Scott Marlowe skrev 2010-01-03 22.03: On Sun, Jan 3, 2010 at 1:10 PM, Robert Gravsjö wrote: I encountered a curious thing today. Simple select queries against a fairly large, ~60M rows, and active, both in reading and writing, suddenly were aweful slow, from milliseconds into 10th of seconds.

Re: [GENERAL] Curious index selection when using a date range

2010-01-03 Thread Scott Marlowe
On Sun, Jan 3, 2010 at 1:10 PM, Robert Gravsjö wrote: > I encountered a curious thing today. Simple select queries against a fairly > large, ~60M rows, and active, both in reading and writing, suddenly were > aweful slow, from milliseconds into 10th of seconds. > > Looking a bit closer revealed th