From: Josh Berkus <josh@agliodbs.com>
To: Joe Conway <mail@joeconway.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 12:12:08 -0700
Message-ID: <4C698D88.6030201@agliodbs.com> (raw)
In-Reply-To: <4C698CAD.2020001@joeconway.com>
References: <4C69827A.409@agliodbs.com>
<4C698CAD.2020001@joeconway.com>
> I've also recently heard a report of vacuum hanging on 8.3.x on Solaris
> Sparc. Any chance you can get a backtrace from a build with debug symbols?
The problem is that we haven't been able to reproduce the bug in
testing. Like I said, it only seems to happen occasionally ... like
maybe once in 10 or 20 (or more?) autovacuums. We've never been seen it
with a manual vacuum at all.
And we can't rebuild the production servers.
--
-- 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, mail@joeconway.com
Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
In-Reply-To: <4C698D88.6030201@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