From: Vivek Khera <khera@kcilink.com>
To: pgsql-performance@postgresql.org
Subject: Re: Avoiding vacuum full on an UPDATE-heavy table
Date: Fri, 21 May 2004 16:36:18 -0400
Message-ID: <x7n041msal.fsf@yertle.int.kciLink.com> (raw)
References: <40AE274F.7020800@lulu.com>
>>>>> "BM" == Bill Montgomery <billm@lulu.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@kciLink.com Rockville, MD +1-301-869-4449 x806
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: khera@kcilink.com
Subject: Re: Avoiding vacuum full on an UPDATE-heavy table
In-Reply-To: <x7n041msal.fsf@yertle.int.kciLink.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox