From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Dan Harris <fbsd@drivefaster.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Quad Opteron stuck in the mud
Date: Wed, 13 Jul 2005 16:18:17 -0400
Message-ID: <20050713201817.GA5450@alvh.no-ip.org> (raw)
In-Reply-To: <862C6AD9-646B-4907-AB18-09F1AD08B5F5@drivefaster.net>
References: <E5E21B7B-FFE0-4D24-8CDD-62179AEBBB92@drivefaster.net>
<42D56772.6020408@arbash-meinel.com>
<862C6AD9-646B-4907-AB18-09F1AD08B5F5@drivefaster.net>
On Wed, Jul 13, 2005 at 01:16:25PM -0600, Dan Harris wrote:
> On Jul 13, 2005, at 1:11 PM, John A Meinel wrote:
>
> >I might be wrong, but there may be something much more substantially
> >wrong than slow i/o.
>
> Yes, I'm afraid of that too. I just don't know what tools I should
> use to figure that out. I have some 20 other databases on this
> system, same schema but varying sizes, and the small ones perform
> very well. It feels like there is an O(n) increase in wait time that
> has recently become very noticeable on the largest of them.
I'd guess it's stuck on some lock. Try that EXPLAIN, and when it
blocks, watch the pg_locks view for locks not granted to the process
executing the EXPLAIN. Then check what else is holding the locks.
--
Alvaro Herrera (<alvherre[a]alvh.no-ip.org>)
"La rebeldÃa es la virtud original del hombre" (Arthur Schopenhauer)
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: alvherre@alvh.no-ip.org, fbsd@drivefaster.net
Subject: Re: Quad Opteron stuck in the mud
In-Reply-To: <20050713201817.GA5450@alvh.no-ip.org>
* 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