From: | Vivek Khera <khera(at)kcilink(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Avoiding vacuum full on an UPDATE-heavy table |
Date: | 2004-05-21 20:36:18 |
Message-ID: | x7n041msal.fsf@yertle.int.kciLink.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
>>>>> "BM" == Bill Montgomery <billm(at)lulu(dot)com> writes:
BM> Is there any way to avoid doing a periodic VACUUM FULL on this table,
BM> given the fairly radical usage pattern? Or is the (ugly) answer to
BM> redesign our application to avoid this usage pattern?
I'll bet upgrading to 7.4.2 clears up your problems. I'm not sure if
it was in 7.3 or 7.4 where the index bloat problem was solved. Try to
see if just reindexing will help your performance. Also, run a plain
vacuum at least nightly so that your table size stays reasonable. It
won't take much time on a table with only 50k rows in it.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera(at)kciLink(dot)com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Montgomery | 2004-05-21 21:29:33 | Re: Avoiding vacuum full on an UPDATE-heavy table |
Previous Message | Marty Scholes | 2004-05-21 20:10:56 | Re: PostgreSQL caching |