| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-performance(at)postgresql(dot)org, "Denis Lussier" <denisl(at)enterprisedb(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "korryd(at)enterprisedb(dot)com" <korryd(at)enterprisedb(dot)com>, "Jonah H(dot) Harris" <jharris(at)enterprisedb(dot)com>, "Craig A(dot) James" <cjames(at)modgraph-usa(dot)com> |
| Subject: | Re: Simple join optimized badly? |
| Date: | 2006-10-08 23:16:37 |
| Message-ID: | 12915.1160349397@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Now, if you were offering us a patch to auto-populate the statistics as a
> table is loaded, I'd be all for that.
Curiously enough, I was just thinking about that after reading Craig's
post. autovacuum will do this, sort of, if it's turned on --- but its
reaction time is measured in minutes typically so that may not be good
enough.
Another thing we've been beat up about in the past is that loading a
pg_dump script doesn't ANALYZE the data afterward...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig A. James | 2006-10-09 01:07:22 | Re: Simple join optimized badly? |
| Previous Message | Josh Berkus | 2006-10-08 23:05:02 | Re: Simple join optimized badly? |