Greg Smith <g...@2ndquadrant.com> writes:
> It sounds like random pgbench run for a while would certainly expose the
> same thing you're concerned about eventually.
Yeah. Actually the odd thing about it is that the crash seemed to
invariably be on conflicting pgbench_accounts updates, which is a fairly
low-contention table in this test design (but the bug turned it into
high-contention). What I would have expected is crashes on the very
similar updates to pgbench_branches, which is designed to be
high-contention. It might be that there is some other effect going on
here that explains why that wasn't happening. Need to go back and look
more closely.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
