| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Anibal David Acosta" <aa(at)devshock(dot)com> |
| Cc: | "'Craig Ringer'" <ringerc(at)ringerc(dot)id(dot)au>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: autovacuum, exclude table |
| Date: | 2011-12-12 15:26:10 |
| Message-ID: | 18792.1323703570@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Anibal David Acosta" <aa(at)devshock(dot)com> writes:
> Tables has insert (in bulk every 3 minutes) and delete one per day (delete records older than XX days)
No updates at all, just inserts and a daily delete?
If so, you're wasting your time even thinking about suppressing
autovacuum, because it won't fire on this table except after the daily
delete, which is exactly when you need it to.
Also, if you suppress autovacuum you also suppress autoanalyze,
which is something that *will* fire after large inserts, and probably
should. At least, this usage pattern doesn't suggest to me that it's
clearly safe to run without up-to-date stats.
Right offhand, I'm not convinced either that you have a problem, or that
turning off autovacuum would fix it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-12-12 16:38:04 | Re: copy vs. C function |
| Previous Message | Heikki Linnakangas | 2011-12-12 15:16:08 | Re: autovacuum, exclude table |