From: Emre Hasegeli <emre.hasegeli@tart.com.tr>
To: pgsql-performance@postgresql.org, pgsql <pgsql-general@postgresql.org>
Cc: dba@tart.com.tr
Subject: Re: PostgreSQL 9.2.3 performance problem caused Exclusive locks
Date: Tue, 12 Mar 2013 21:17:33 +0200
Message-ID: <op.wtuk7jp4k2xoe5@localhost.localdomain> (raw)
In-Reply-To: <op.wtmkrq0nk2xoe5@hasegeli.local>
References: <op.wtmkrq0nk2xoe5@hasegeli.local>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
2013-03-08 13:27:16 +0200 Emre Hasegeli <emre.hasegeli@tart.com.tr>:
> PostgreSQL writes several following logs during the problem which I never
> saw before 9.2.3:
>
> LOG: process 4793 acquired ExclusiveLock on extension of relation
> 305605 of database 16396 after 2348.675 ms
I tried
* to downgrade to 9.2.2
* to disable autovacuum
* to disable synchronous commit
* to write less on the big tables
* to increase checkpoint segments
* to increase max connections
* to move pg_xlog to sepe
None of them helps to avoid downtimes. I could not find anything related
to it? Do you have any idea? Have you ever experience something like this?
--
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: emre.hasegeli@tart.com.tr, pgsql-general@postgresql.org, dba@tart.com.tr
Subject: Re: PostgreSQL 9.2.3 performance problem caused Exclusive locks
In-Reply-To: <op.wtuk7jp4k2xoe5@localhost.localdomain>
* 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