Re: PQisBusy() always busy - Mailing list pgsql-novice

From Merlin Moncure
Subject Re: PQisBusy() always busy
Date
Msg-id CAHyXU0zppGU21hxnEwtK9pGmoXtfP8Wg7hKHfGFGNWNrNGXMVg@mail.gmail.com
Whole thread Raw
In response to Re: PQisBusy() always busy  (bradg <bg4all@me.com>)
List pgsql-novice
On Tue, Sep 13, 2011 at 7:50 PM, bradg <bg4all@me.com> wrote:
> Thanks for your thoughtful, detailed response. I also took your warnings to
> heart and resolved the underlying problem in my code without resorting to
> threads. I have both the blocking and nonblocking functions working without
> any issues.
>
> Except one. Speed.
>
> When I use the blocking function on a select query for 102 records, the time
> is 0.645284 seconds. When I use the nonblocking version, the time is
> 52.000426 seconds. The application pgAdmin3 takes 1.6 seconds.
>
> Does that seem right?

It does not.  In fact, if you look at the internal libpq code, you'll
notice that they all run through the same internal call -- something
is amiss. What happens when you immediately try to get the result
after sending the query?

merlin

pgsql-novice by date:

Previous
From: rox
Date:
Subject: Can I capture created key id's, work with them, then return themlater?
Next
From: rox
Date:
Subject: What type is required to capture the RETURNING from anUpdate?