From: Josh Berkus <josh@agliodbs.com>
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?
Date: Wed, 18 Aug 2010 11:49:15 -0700
Message-ID: <4C6C2B2B.9060501@agliodbs.com> (raw)
In-Reply-To: <19969.1281986537@sss.pgh.pa.us>
References: <4C69827A.409@agliodbs.com>
<19969.1281986537@sss.pgh.pa.us>
> 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
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: josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
In-Reply-To: <4C6C2B2B.9060501@agliodbs.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