Re: BUG #8470: 9.3 locking/subtransaction performance regression

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: os(at)ohmu(dot)fi
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8470: 9.3 locking/subtransaction performance regression
Date: 2013-09-25 14:26:19
Message-ID: 20130925142618.GT4832@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

os(at)ohmu(dot)fi wrote:

> The following code performs a lot slower on PostgreSQL 9.3.0 than on
> PostgreSQL 9.2.4:
>
> DROP TABLE IF EXISTS tmp;
> CREATE TABLE tmp (id BIGSERIAL, vals BIGINT[]);
> DO $$
> DECLARE
> r_id BIGINT;
> n BIGINT;
> BEGIN
> FOR n IN 1..1000 LOOP
> BEGIN
> SELECT id INTO r_id FROM tmp WHERE array_length(vals, 1) < 100
> LIMIT 1 FOR UPDATE NOWAIT;

Most likely, this is caused by the new tuple lock code in 9.3. I can't
look at this immediately but I will give it a look as soon as I'm able.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stuart Bishop 2013-09-25 19:49:48 Re: BUG #8450: pg_basebackup blocks until WAL archiving successful
Previous Message os 2013-09-25 13:34:47 BUG #8470: 9.3 locking/subtransaction performance regression