Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
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
References: <op.wtmkrq0nk2xoe5@hasegeli.local>
Date: Tue, 12 Mar 2013 21:17:33 +0200
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Emre Hasegeli" <emre.hasegeli@tart.com.tr>
Organization: 
 =?utf-8?B?VGFydCDEsG50ZXJuZXQgVGVrbm9sb2ppbGVyaSBUaWNhcmV0IEHFng==?=
Message-ID: <op.wtuk7jp4k2xoe5@localhost.localdomain>
In-Reply-To: <op.wtmkrq0nk2xoe5@hasegeli.local>
User-Agent: Opera Mail/12.12 (Linux)
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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