Re: assertion failure 9.3.4

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: assertion failure 9.3.4
Date: 2014-04-22 01:04:48
Message-ID: 5355C030.8010503@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

All,

I've taken a stab at creating a reproduceable test case based on the
characterisitics of the production issues I'm seeing. But clearly
there's an element I'm missing, because I'm not able to produce the bug
with a pgbench-based test case.

My current test has FKs, updating both FK'd tables, updating both
indexed and non-indexed columns, and doing multiple updates in the same
transaction, and lock-blocking.

Files are attached in case someone has better ideas. queue_bench.sql is
the setup file, and then you do:

pgbench -n -T 600 -c 15 -j 5 -f queue_adder.bench -f queue_worker.bench
-f queue_worker.bench -f queue_worker.bench -f queue_worker.bench {dbname}

... or whatever levels of c and j make sense on your hardware.

FWIW, this particular test case might make a nice destruction test case
for replication testing, too.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

Attachment Content-Type Size
queue_bench.sql text/x-sql 2.5 KB
queue_adder.bench text/plain 101 bytes
queue_worker.bench text/plain 95 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-04-22 01:06:35 Re: Perfomance degradation 9.3 (vs 9.2) for FreeBSD
Previous Message Peter Geoghegan 2014-04-22 00:59:34 Re: Clock sweep not caching enough B-Tree leaf pages?