| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Cory 'G' Watson" <gphat(at)cafes(dot)net> |
| Cc: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Profiling |
| Date: | 2002-12-17 14:49:16 |
| Message-ID: | 6741.1040136556@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Cory 'G' Watson" <gphat(at)cafes(dot)net> writes:
> I assume I do not need a --analyze, since that table has no indexes.
Whether you need analyze or not has nothing to do with whether there
are indexes. You probably don't need it once an hour, but maybe once
a day would be good.
> Should I vacuum the entire DB?
Overkill; just get the heavily-updated table(s). A DB-wide vacuum must
be done occasionally, but again once-a-day would be plenty.
> Any other settings I should look at?
Free space map (fsm) settings must be adequate to keep track of the free
space in your tables.
However, all of this relates only to keeping performance good on the
table with lots of updates. If you are seeing progressive degradation
on a table that only gets INSERTs, then there's something else going on.
AFAIR you didn't show us an EXPLAIN ANALYZE for the principal query?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2002-12-17 16:18:02 | Re: Profiling |
| Previous Message | Shridhar Daithankar | 2002-12-17 14:29:42 | Re: Profiling |