Re: [HACKERS] libpq thread safety

From: Manfred Spraul <manfred(at)colorfullife(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] libpq thread safety
Date: 2004-03-22 06:12:59
Message-ID: 405E83EB.9000701@colorfullife.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian wrote:

>I could not get this patch to compile. I am getting a failure because
>BSD/OS doesn't have pthread_rwlock_wrlock(). I am concerned other
>platforms might not have it either.
>
>
I feared that. I'll switch to pthread_mutex_lock()+_unlock().
pthread_rwlock_wrlock()+_unlock was faster in some tests - wrlocks do
not need to be async signal safe.

I'll send a new patch.
--
Manfred

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Karel Zak 2004-03-22 06:46:23 Re: COPY formatting
Previous Message Bruce Momjian 2004-03-22 06:12:03 Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use threads

Browse pgsql-patches by date

  From Date Subject
Next Message Karel Zak 2004-03-22 07:05:28 Re: pstrndup()
Previous Message Bruce Momjian 2004-03-22 06:12:03 Re: [PATCHES] UnixWare/CVS Tip/initdb.c needs to use threads