| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Browne <cbbrowne(at)acm(dot)org>, postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Automatic free space map filling |
| Date: | 2006-03-03 00:36:18 |
| Message-ID: | 44078F82.9040601@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Csaba Nagy wrote
> From my POV, there must be a way to speed up vacuums on huge tables and
> small percentage of to-be-vacuumed tuples... a 200 million rows table
> with frequent updates of the _same_ record is causing me some pain right
> now. I would like to have that table vacuumed as often as possible, but
> right now it only works to do it once per week due to load problems on
> long-running transactions preventing vacuuming other tables.
Are you running 8.1? If so, you can use autovacuum and set per table
thresholds (read vacuum aggressivly) and per table cost delay settings
so that the performance impact is minimal. If you have tried 8.1
autovacuum and found it unhelpful, I would be curious to find out why.
Matt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-03 01:05:59 | Re: Foreign keys for non-default datatypes |
| Previous Message | John Gray | 2006-03-03 00:27:20 | Re: PG Extensions: Must be statically linked? |