| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange buildfarm failure on lionfish |
| Date: | 2007-07-24 17:56:14 |
| Message-ID: | 14133.1185299774@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> What I don't understand is what you mean with it "obliterating" the
> stats for a table.
The point seems to be that if there is no pg_statistic data for these
tables, we fall back to default estimates of the selectivity of the
WHERE clauses, and those produce rowcount estimates that are pretty
far away from the truth. As soon as some pg_statistic entries
exist, we obtain better rowcount estimates, and that changes the join
plan.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2007-07-24 19:05:54 | Re: pgcrypto & strong ciphers limitation |
| Previous Message | Alvaro Herrera | 2007-07-24 17:55:57 | Re: strange buildfarm failure on lionfish |