From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Tim Jones" <TJones(at)optio(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: strange query behavior |
Date: | 2006-12-14 17:48:35 |
Message-ID: | 22464.1166118515@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
"Tim Jones" <TJones(at)optio(dot)com> writes:
> 18,273,008 rows in observationresults
> [ and n_distinct = 12942 ]
OK, so the estimated rowcounts are coming from those two numbers.
It's notoriously hard to get a decent n_distinct estimate from a small
sample :-(, and I would imagine the number of batteryidentifiers is
really a lot more than 12942?
What you need to do is increase the statistics target for
observationresults.batteryidentifier (see ALTER TABLE) and re-ANALYZE
and see if you get a saner n_distinct in pg_stats. I'd try 100 and
then 1000 as target. Or you could just increase the global default
target (see postgresql.conf) but that might be overkill.
It's still a bit odd that the case with two batteryidentifiers was
estimated fairly accurately when the other wasn't; I'll go look into
that. But in any case you need better stats if you want good plans.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-14 18:30:15 | Re: strange query behavior |
Previous Message | Bruno Wolff III | 2006-12-14 17:48:09 | Re: File Systems Compared |