pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Lee Kindness <lkindness@csl.co.uk>
Cc: Philip Yarra <philip@utiba.com>
Cc: Michael Meskes <meskes@postgresql.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: ECPG thread-safety
Date: Wed, 23 Apr 2003 14:15:59 -0400 (EDT)
Message-ID: <200304231815.h3NIFxe07882@candle.pha.pa.us> (raw)
In-Reply-To: <16038.21258.950904.455466@kelvin.csl.co.uk>


I have libpq thread-safe patch in my queue:

	http://momjian.postgresql.org/cgi-bin/pgpatches

Once I have a way to test thread flags for various OS's, I will apply
it.  Maybe you guys can help with that too.

---------------------------------------------------------------------------

Lee Kindness wrote:
> Philip Yarra writes:
>  > I've had a few tries at testing the ECPG threadsafe patch, but so
>  > far no luck, probably due to my own lack of experience. Can someone
>  > help me out with how to test this?
>  > 
>  > So far I have:
>  > - run configure
>  > - applied Lee's patch to the source tree for 7.3.2
>  > - edited src/Makefile.global, adding -pthread to CFLAGS and and
>  > -lpthread to LIBS
>  > - make and make install
>  > - make our own pthread'd app, linking against newly installed pgsql
>  > Then when I run our app with 3 DB threads, I can watch 2 of the threads fai=
>  > l=20
>  > to return from EXEC SQL, which is exactly the same behaviour we used to get.
>  > 
>  > Can anyone point me in the right direction? I'm building on RedHat Linux 7.=
>  > 3=20
>  > on Intel, using all standard tools for that version (except updated bison=
>  > =20
>  > from 1.35 to 1.875). So gcc 2.96, gmake 3.79.1, etc. Let me know if more=20
>  > details are required.
> 
> Even with this patch you'll still be limited by the underlying
> libpq. So for example you cannot share a connection between threads
> without implementing locking to prevent multiple access to that
> connection.
> 
> I guess the best way would be to open a named connection for EACH
> thread. This SHOULD work, but again not tested...
> 
> L.
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073




view thread (35+ messages)  latest in thread

Message-ID: <200304231815.h3NIFxe07882@candle.pha.pa.us>
Permalink:  ../200304231815.h3NIFxe07882@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200304231815.h3NIFxe07882@candle.pha.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: pgman@candle.pha.pa.us, lkindness@csl.co.uk, philip@utiba.com, meskes@postgresql.org
  Subject: Re: ECPG thread-safety
  In-Reply-To: <200304231815.h3NIFxe07882@candle.pha.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox