Re: thread safety on clients - Mailing list pgsql-hackers

From Tom Lane
Subject Re: thread safety on clients
Date
Msg-id 22633.1260561393@sss.pgh.pa.us
Whole thread Raw
In response to Re: thread safety on clients  (Greg Smith <greg@2ndquadrant.com>)
Responses Re: thread safety on clients  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Greg Smith <greg@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


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: thread safety on clients
Next
From: Zdenek Kotala
Date:
Subject: Re: [PATCH] dtrace probes for memory manager