| From: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Benjamin Krajmalnik <kraj(at)illumen(dot)com>, pgsql-admin(at)postgresql(dot)org, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net> |
| Subject: | Re: pg_clog questions |
| Date: | 2006-05-26 02:20:46 |
| Message-ID: | 447665FE.5010905@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Alvaro Herrera wrote:
> Tom Lane wrote:
>> Hm. I believe that autovac only does database-wide vacuums when it
>> thinks they're necessary to prevent transaction wraparound failures.
>> Which would mean that it'd let pg_clog grow to something on the order
>> of half a gig before any truncation would happen. That's probably
>> insufficiently aggressive :-(
>>
>> Alvaro, Matthew, any thoughts about improving that?
Not really. Alvara mentioned reducing the constant that we test against
for DB wide vacuum. I'm a little concerned that might result is
database-wide vacuums more often than desired, but I don't see a better
answer off the top of my head.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | renneyt@yahoo.com | 2006-05-26 04:50:50 | PG_DUMP |
| Previous Message | Benjamin Krajmalnik | 2006-05-25 22:43:30 | Re: pg_clog questions |