| From: | Chris Browne <cbbrowne(at)acm(dot)org> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Simple join optimized badly? |
| Date: | 2006-10-09 02:58:26 |
| Message-ID: | 60hcye8ab1.fsf@dba2.int.libertyrms.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) writes:
> Another thing we've been beat up about in the past is that loading a
> pg_dump script doesn't ANALYZE the data afterward...
Do I misrecall, or were there not plans (circa 7.4...) to for pg_dump
to have an option to do an ANALYZE at the end?
I seem to remember some dispute as to whether the default should be to
include the ANALYZE, with an option to suppress it, or the opposite...
--
(reverse (concatenate 'string "ofni.sesabatadxunil" "@" "enworbbc"))
http://www3.sympatico.ca/cbbrowne/wp.html
"You can measure a programmer's perspective by noting his attitude on
the continuing vitality of FORTRAN." -- Alan J. Perlis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2006-10-09 03:38:34 | Re: Simple join optimized badly? |
| Previous Message | Craig A. James | 2006-10-09 02:46:00 | Re: Simple join optimized badly? |