Re: Status of autovacuum and the sporadic stats failures ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Status of autovacuum and the sporadic stats failures ?
Date: 2007-02-06 21:57:47
Message-ID: 21268.1170799067@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> I'm tempted to propose replacing the fixed sleep with a short plpgsql
>> function that sleeps for a second, checks to see if the stats have
>> changed, repeats if not; giving up only after perhaps 30 seconds.
>>
>> It'd be interesting to try to gather stats on the length of the delay
>> taken, but I don't see a good way to do that within the current
>> regression-test infrastructure.

> Have it log something that will appear on the postmaster log but not the
> client log? Buildfarm members mostly post their complete postmaster
> logs, and we could postprocess those.

Or even just eyeball them. Good idea --- I'll do it as soon as I get a
chance to catch my breath. Today's a bit busy :-(

Or if someone else wants to run with the idea, go for it.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2007-02-06 22:25:29 Re: proposed todo: use insert/update returning anywhere a table is allowed
Previous Message Merlin Moncure 2007-02-06 21:54:20 proposed todo: use insert/update returning anywhere a table is allowed