| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Nathan Boley" <npboley(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Josh Berkus" <josh(at)agliodbs(dot)com>, "jd(at)commandprompt(dot)com" <jd(at)commandprompt(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Vladimir Sitnikov" <sitnikov(dot)vladimir(at)gmail(dot)com>, "Greg Smith" <gsmith(at)gregsmith(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: benchmarking the query planner |
| Date: | 2008-12-12 16:35:57 |
| Message-ID: | 603c8f070812120835x7a6b7588icdf6e876239a80d1@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Which raises the issue, if we could get better statistics by passing
> the whole table, why not do that when VACUUM ANALYZE is run?
I think the reason is "because the next autovacuum would undo it".
Perhaps a table-level option to scan the whole table instead of
estimating would be appropriate?
.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2008-12-12 16:40:57 | Re: benchmarking the query planner |
| Previous Message | Robert Haas | 2008-12-12 16:34:06 | Re: Updates of SE-PostgreSQL 8.4devel patches (r1268) |