[PyGreSQL] Thread safety (again)

[Ken Kinder]

So let me get this straight:

You spawn two threads: one runs a query. The other does not touch the
database connection. And the second has problems? That doesn't make sense
-- how could it be effected by PyGreSQL if it doesn't do anything with it?

So what version of PyGreSQL does your patch work on? The devel or stable?

--
Ken Kinder
www.kenkinder.com

On Sun, 9 Apr 2000, Jerome ALET wrote:

> On Fri, Apr 07, 2000 at 07:11:10PM -0600, Ken Kinder wrote:
> >    Ok, let me get this straight... I can have a Pygresql-using program, 
> > provided that I don't have two queries running concurrently on the same 
> > object?
> 
> I've personnally not tested this, either with or without my patch.
> 
> What I think is:
> 
> if you use two different database connections it should be OK, as long as 
> PygreSQL is thread safe.
> 
> if you use the same database connection problems may appear, and you
> have to test it, because it also depends on libpq and the postgresql
> backend being thread safe.
> 
> I've only tested one thread which does queries and another which does
> non database related stuff: without my patch the second thread
> is blocked during each query, with my patch the second thread
> continues to run and no problem appears.
> 
> bye,
> Jerome
> 
> _______________________________________________
> PyGreSQL mailing list
> PyGreSQL at vex.net
> http://mail.vex.net/mailman/listinfo/pygresql
>