From: Robert Becker Cope <robert@gonkgonk.com>
To: bhurt@janestcapital.com
To: pgsql-performance@postgresql.org
To: pgsql-novice@postgresql.org
Subject: Re: Postgres locking up?
Date: Fri, 29 Sep 2006 19:53:46 -0500
Message-ID: <OF7BFE9B02.F9B5036D-ON862571F9.0004ECA0@bytestacker.com> (raw)
Brian Hurt <bhurt@janestcapital.com> wrote:
> I'm experiencing a problem with our postgres database. Queries that
> normally take seconds suddenly start taking hours, if they complete at
> all.
Do you have any long running transactions? I have noticed that with Postgres
8.1.x, a long running transaction combined with other transactions over a long
enough time period can very predictably lead to this type of behavior
One simple way to see if you have any long running transactions is to look for
PIDs that are "idle in transaction" for long periods of time.
robert
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-performance@postgresql.org
Cc: robert@gonkgonk.com, bhurt@janestcapital.com, pgsql-novice@postgresql.org
Subject: Re: Postgres locking up?
In-Reply-To: <OF7BFE9B02.F9B5036D-ON862571F9.0004ECA0@bytestacker.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