| From: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Euler Taveira de Oliveira" <euler(at)timbira(dot)com> |
| Cc: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, "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 18:57:46 |
| Message-ID: | 603c8f070812121057u275e358bw9a62d19631e03101@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> Perhaps a table-level option to scan the whole table instead of
>> estimating would be appropriate?
>>
> ANALYZE FULL foo ?
I was thinking more like a flag that you could set on the table
itself, that would apply to all future analyzes.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2008-12-12 19:08:38 | Re: benchmarking the query planner |
| Previous Message | Euler Taveira de Oliveira | 2008-12-12 18:44:56 | Re: benchmarking the query planner |