From: Josh Berkus <josh@agliodbs.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: Anyone seen this kind of lock pileup?
Date: Wed, 17 Nov 2010 14:02:54 -0800
Message-ID: <4CE4510E.9050302@agliodbs.com> (raw)
In-Reply-To: <24934.1290031132@sss.pgh.pa.us>
References: <4CE412F4.4090101@agliodbs.com>
<24934.1290031132@sss.pgh.pa.us>
> Hmm ... can you extract a test case? Or at least strace the backends
> involved?
No, and no. Strace was the first thing I thought of, but I'd have to
somehow catch one of these backends in the 3 seconds it's locked. Not
really feasible.
It might be possible to construct a test case, depending on how much the
user wants to spend on the problem. I'd estimate that a test case would
take 8-12 hours of my time to get working, given the level of activity
and concurrency required.
--
-- 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-performance@postgresql.org
Cc: josh@agliodbs.com, tgl@sss.pgh.pa.us
Subject: Re: Anyone seen this kind of lock pileup?
In-Reply-To: <4CE4510E.9050302@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