From: Scott Marlowe <scott.marlowe@gmail.com>
To: Bryce Nesbitt <bryce2@obviously.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Postgres entering zombie state once a week in production evnvironment
Date: Tue, 14 Apr 2009 01:29:02 -0600
Message-ID: <dcc563d10904140029j78b70370hf2b385a4fad82e76@mail.gmail.com> (raw)
In-Reply-To: <49E42C72.9070902@obviously.com>
References: <49E42C72.9070902@obviously.com>
On Tue, Apr 14, 2009 at 12:25 AM, Bryce Nesbitt <bryce2@obviously.com> wrote:
> We have a medium scale installation of Postgres 8.3 that is freezing about
> once a week. I'm looking for any hints on how to diagnose the situation, as
> nothing is logged.
>
> The system is matched pair of Sunfire servers, running Debian Etch with a
> 2.6.18-6-amd64 kernel, PostgreSQL 8.3.4, and DRBD 8.0.13.
>
> During a failed state, pg_stat_activity will show hundreds of statements
> pending. query_start will show the statements arriving at a normal rate (a
> few per second), but clearly they never complete. The bulk of these
> statement are a simple select that starts each web session, a statement that
> generally completes in tenths of milliseconds. Restarting postgres restores
> normal operation, at the loss of all chance of figuring out what was wrong.
What does pg_locks say during this time? Specifically about locks
that aren't granted?
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-sql@postgresql.org
Cc: scott.marlowe@gmail.com, bryce2@obviously.com
Subject: Re: Postgres entering zombie state once a week in production evnvironment
In-Reply-To: <dcc563d10904140029j78b70370hf2b385a4fad82e76@mail.gmail.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