Re: thread safety on clients

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: thread safety on clients
Date: 2009-12-11 01:13:36
Message-ID: 4B219CC0.4020507@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> Peter Eisentraut wrote:
>
>>> if i remove the -j option then it runs without a problem
>>>
>> Possibly related to the incomplete removal of the enable-thread-safety
>> option that I just posted about.
>>
>
> I thought about that but I can't figure out how that would affect
> pgbench.
>
The "-j" option is the recent addition to pgbench that causes it to
launch multiple client threads when enabled, each handling a subset of
the transactions. There's blocks of codes in pgbench.c now that depend
on having sane values for thread safety in libpq. That it may be
detecting the wrong thing and operating in an unsafe way after the
recent change is what Peter's suggesting. This is good, actually,
because I don't think we had many client-side thread-safety tests
floating around to catch problems in this area before.

--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Takahiro Itagaki 2009-12-11 01:16:56 Re: Largeobject Access Controls (r2460)
Previous Message Bruce Momjian 2009-12-11 01:11:19 Re: explain output infelicity in psql