Message-ID: <4C6C2B2B.9060501@agliodbs.com>
Date: Wed, 18 Aug 2010 11:49:15 -0700
From: Josh Berkus <josh@agliodbs.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Return of the Solaris vacuum polling problem -- anyone
	remember this?
References: <4C69827A.409@agliodbs.com> <19969.1281986537@sss.pgh.pa.us>
In-Reply-To: <19969.1281986537@sss.pgh.pa.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


> What I find interesting about that trace is the large proportion of
> writes.  That appears to me to indicate that it's *not* a matter of
> vacuum delays, or at least not just a matter of that.  The process seems
> to be getting involved in having to dump dirty buffers to disk.  Perhaps
> the background writer is malfunctioning?

You appear to be correct in that it's write-related.  Will be testing on
what specificially is producing it.

Note that this is one of two ostensibly duplicate servers, and the issue
has never appeared on the other server.

-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com