From: Markus Schaber <schabi@logix-tt.com>
To: pgsql-performance@postgresql.org
Subject: Re: Default autovacuum settings too conservative
Date: Tue, 07 Feb 2006 13:39:34 +0100
Message-ID: <43E89506.40903@logix-tt.com> (raw)
In-Reply-To: <20060207072621.GI13592@pervasive.com>
References: <20060201211633.GM95850@pervasive.com>
<43E12A03.6070906@zeut.net>
<20060207050545.GZ1240@pervasive.com>
<m38xsn4rvm.fsf@mobile.int.cbbrowne.com>
<20060207072621.GI13592@pervasive.com>
Hi, Jim,
Jim C. Nasby wrote:
> What we really need is a replacement for vacuum_delay that takes
> PostgreSQL generated IO activity into account...
There are also other ideas which can make vacuum less painfull:
- Use a "delete"-map (like the free space map) so vacuum can quickly
find the pages to look at.
- Have vacuum end its transaction after a certain amount of work, and
restart at the same page later.
- Have vacuum full search good candidates with non-stopping lock (and
usage of delete-map and fsm), then doing {lock, recheck, move, unlock}
in small amounts of data with delay between.
- Introducing some load measurement, and a pressure measurement (number
of deleted rows, TID wraparound etc.). Then start vacuum when load is
low or pressure is very high. Tune other parameters (like "certain
amount of work" depending on those measures.
All of them are a lot of code to hack, but although I'm not a postgresql
core developer, I am keen enough to invite you to send patches. :-)
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
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: schabi@logix-tt.com
Subject: Re: Default autovacuum settings too conservative
In-Reply-To: <43E89506.40903@logix-tt.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