From: Tom Lane <tgl@sss.pgh.pa.us>
To: brians@ucsd.edu
Cc: pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] client connections to libpq
Date: Sat, 17 Oct 1998 11:51:38 -0400
Message-ID: <13839.908639498@sss.pgh.pa.us> (raw)
In-Reply-To: <98101702533702.00730@fidessa>
"Brian E. Sanders" <brian@vingulf.org> writes:
> I have posted on this twice before about this question, but what does
> this mean in the 6.4-beta2 HISTORY file:
> Libpq now allows asynchronous clients(Tom)
If you posted, I didn't see it...
What it means is that applications using libpq are no longer forced to
wait while the server processes a query. It used to be that to do a
query, you had to call PQexec(), and control wouldn't come back from
that routine until the database server processed your query (and
returned *all* the data, if it was a SELECT). Not cool if you needed
to do other things, like handle an interactive user interface or watch
other data source connections.
Of course PQexec still works like that, since we're not in the business
of breaking existing code. But there are now some additional entry
points, PQsendQuery and PQgetResult, that allow you to send off a
query and then get on with your other business until the result comes
back. (PQexec is actually now built on top of those routines.)
If this sounds like something you have a use for, please see the new
libpq documentation for details. I can answer additional questions,
but first I'd like to find out if the doc still needs work ;-)
regards, tom lane
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: tgl@sss.pgh.pa.us, brians@ucsd.edu, pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] client connections to libpq
In-Reply-To: <13839.908639498@sss.pgh.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