Re: selects from large tables
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Charles H. Woloszynski" <chw@clearmetrix.com>
Cc: Nikk Anderson <Nikk.Anderson@parallel.ltd.uk>, "'Stephan Szabo'" <sszabo@megazone23.bigpanda.com>, pgsql-performance@postgresql.org
Date: 2002-11-18T16:25:27Z
Lists: pgsql-performance
"Charles H. Woloszynski" <chw@clearmetrix.com> writes: > Are you doing vaccums on these tables? I was under the understanding > that the estimated row count should be close to the real row count > returned, and when it is not (as it looks in your case), the primary > reason for the disconnect is that the stats for the tables are > out-of-date. The fact that he's using 7.1 doesn't help any; the statistics mechanisms in 7.1 are pretty weak compared to 7.2. > Also, do you do any clustering of the data (since the queries are mostly > time limited)? I am wondering if the system is doing lots of seeks to > get the data (implying that the data is all over the disk and not > clustered). It would also be interesting to try a two-column index ordered the other way (timestamp as the major sort key instead of ID). Can't tell if that will be a win without more info about the data properties, but it's worth looking at. regards, tom lane