pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
Date: Mon, 16 Aug 2010 17:24:23 -0400
Message-ID: <1281992840-sup-6951@alvh.no-ip.org> (raw)
In-Reply-To: <1281992147-sup-9595@alvh.no-ip.org>
References: <4C69827A.409@agliodbs.com>
	<4C698CAD.2020001@joeconway.com>
	<4C698D88.6030201@agliodbs.com>
	<4C69A3D7.8020609@joeconway.com>
	<1281992147-sup-9595@alvh.no-ip.org>

Excerpts from Alvaro Herrera's message of lun ago 16 16:58:31 -0400 2010:

> I suspect that the problem may lie in the "cost_delay rebalance" code in
> autovacuum.

Hmm, so we have this code:

void
AutoVacuumUpdateDelay(void)
{
	if (MyWorkerInfo)
	{
		VacuumCostDelay = MyWorkerInfo->wi_cost_delay;
		VacuumCostLimit = MyWorkerInfo->wi_cost_limit;
	}
}

where the MyWorkerInfo bits come from shared memory and can be modified
by other autovac worker processes.  We could read an incomplete value
into our variables.  But this only makes sense if an "int" variable can
be subject to a partial read/write, which we already assume not to be so
(c.f. GetNewTransactionId).

In any case, if you happen to see this reoccur, could you please attach
GDB to the misbehaving worker and see what VacuumCostDelay and
VacuumCostLimit print out as?

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (31+ messages)  latest in thread

Message-ID: <1281992840-sup-6951@alvh.no-ip.org>
Permalink:  ../1281992840-sup-6951@alvh.no-ip.org/
Also on:    postgresql.org/message-id/1281992840-sup-6951@alvh.no-ip.org

 · 

reply
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-hackers@postgresql.org
  Cc: alvherre@commandprompt.com, mail@joeconway.com, josh@agliodbs.com
  Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
  In-Reply-To: <1281992840-sup-6951@alvh.no-ip.org>

* 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