Skip site navigation (1) Skip section navigation (2)

Re: PQisBusy() always busy

From: bradg <bg4all(at)me(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: PQisBusy() always busy
Date: 2011-09-12 22:44:07
Message-ID: 1315867447753-4796276.post@n5.nabble.com (view raw or flat)
Thread:
Lists: pgsql-novice
I know it must sound stupid, but...

My code is simple and works exactly the way I want it to with the blocking
functions PQexecParams() and PQexecPrepared(). I'm trying to extend it with
asynchronous functions so I can execute queries both ways.

But I seem to be losing a lot of time on this so my thought was to just use
the blocking functions in a separate thread. Hence my question whether or
not they are thread safe.

Do you know if they are?

Thanks

--
View this message in context: http://postgresql.1045698.n5.nabble.com/PQisBusy-always-busy-tp4793847p4796276.html
Sent from the PostgreSQL - novice mailing list archive at Nabble.com.

In response to

Responses

pgsql-novice by date

Next:From: SamuelStarDate: 2011-09-13 01:40:42
Subject: Unable to start postgres service (8.4)
Previous:From: Merlin MoncureDate: 2011-09-12 22:23:58
Subject: Re: PQisBusy() always busy

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group