From: Tom Lane <tgl@sss.pgh.pa.us>
To: Martin Foster <martin@ethereal-realms.org>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Clearing rows periodically
Date: Fri, 18 Jul 2003 09:31:07 -0400
Message-ID: <23422.1058535067@sss.pgh.pa.us> (raw)
In-Reply-To: <3F1799D0.1010009@ethereal-realms.org>
References: <3F13E18A.21241.4B86CB0@localhost>
<3F17E2A2.28685.45CC782@localhost>
<3F1799D0.1010009@ethereal-realms.org>
Martin Foster <martin@ethereal-realms.org> writes:
> My question is, should the purging of rows be done more often then once
> a day for both tables. Is this why performance seems to take a hit
> specifically?
Given that the hourly purge seems to work well for you, I'd suggest
trying it on both tables.
Non-FULL vacuum is intended to be run *frequently*, say as often as
you've updated or deleted 10% to 50% of the rows in a table. Delaying
it until you've had multiple complete turnovers of the table contents
will cost you.
> As there were too many rows purged for vacuum to
> accurately keep track of?
Only possible if you don't have the FSM parameters set high enough.
Infrequent vacuuming means you need more FSM space, btw.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, martin@ethereal-realms.org
Subject: Re: Clearing rows periodically
In-Reply-To: <23422.1058535067@sss.pgh.pa.us>
References: <3F13E18A.21241.4B86CB0@localhost> <3F17E2A2.28685.45CC782@localhost> <3F1799D0.1010009@ethereal-realms.org> <23422.1058535067@sss.pgh.pa.us>
* 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