| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Scot Kreienkamp" <SKreien(at)la-z-boy(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Vacuum problems |
| Date: | 2009-01-05 18:40:27 |
| Message-ID: | dcc563d10901051040y1d3f7974idbbf7d5932f65bde@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Another strategy to look at is to make autovacuum more aggresive by
putting entries for that one table into the pg_autovacuum table. I
know that table exists in 8.3 but I don't remember if it exists in
older versions or how it works there. But if you have that available
you can make that one relation more aggresively autovacuumed without
affecting the other relations vacuum scheduling. On 8.3 you can set
individual cost delays, and all the other settings you'd need. If 8.2
doesn't support this, look at migrating just for that functionality
alone.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2009-01-05 18:53:05 | Re: does postgres has the same limitation as MySQL? |
| Previous Message | Scott Marlowe | 2009-01-05 18:36:57 | Re: Vacuum problems |