Re: First steps with 8.3 and autovacuum launcher

From: Michael Paesold <mpaesold(at)gmx(dot)at>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: First steps with 8.3 and autovacuum launcher
Date: 2007-10-12 09:08:21
Message-ID: 470F3985.6080702@gmx.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> I think the best way to handle this is to have two limits.
>
> First limit attempts to autovacuum, but can be cancelled.
>
> When we hit second limit, sometime later, then autovacuum cannot be
> cancelled.
>
> That would give us a breathing space if we need it.

Sounds quite reasonable.

Best Regards
Michael Paesold

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Klyukin 2007-10-12 09:39:20 Re: Some questions about mammoth replication
Previous Message Heikki Linnakangas 2007-10-12 09:03:02 Re: Including Snapshot Info with Indexes