From: Joshua Berkus <josh@agliodbs.com>
To: Emre Hasegeli <emre.hasegeli@tart.com.tr>
Cc: dba@tart.com.tr, pgsql-performance@postgresql.org, pgsql <pgsql-general@postgresql.org>
Subject: Re: PostgreSQL 9.2.3 performance problem caused Exclusive locks
Date: Wed, 13 Mar 2013 16:04:58 -0500 (CDT)
Message-ID: <978553984.25691.1363208698441.JavaMail.root@agliodbs.com> (raw)
In-Reply-To: <op.wtuk7jp4k2xoe5@localhost.localdomain>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Emre,
> > LOG: process 4793 acquired ExclusiveLock on extension of relation
> > 305605 of database 16396 after 2348.675 ms
The reason you're seeing that message is that you have log_lock_waits turned on.
That message says that some process waited for 2.3 seconds to get a lock for expanding the size of relation 16396/305605, which is most likely an index. This is most likely due to changes in your application, or an increase in concurrent write activity.
--Josh
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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, emre.hasegeli@tart.com.tr, pgsql-general@postgresql.org
Subject: Re: PostgreSQL 9.2.3 performance problem caused Exclusive locks
In-Reply-To: <978553984.25691.1363208698441.JavaMail.root@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