pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedclient connections to libpq
3+ messages / 3 participants
[nested] [flat]
* client connections to libpq
@ 1998-10-17 09:38 Brian E. Sanders <brian@vingulf.org>
0 siblings, 2 replies; 3+ messages in thread
From: Brian E. Sanders @ 1998-10-17 09:38 UTC (permalink / raw)
To: pgsql-interfaces@hub.org; +Cc: tih@Harmartun.priv.no.tgl
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 someone knowledgeable would just tell me it's too esoteric a question for
the mailing lists, please let me know and I'll look elsewhere.
Brian
--
Brian Sanders, Software Engineer 619.452.6450
http://www.vingulf.org
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [INTERFACES] client connections to libpq
@ 1998-10-17 13:54 Peter T Mount <peter@retep.org.uk>
parent: Brian E. Sanders <brian@vingulf.org>
1 sibling, 0 replies; 3+ messages in thread
From: Peter T Mount @ 1998-10-17 13:54 UTC (permalink / raw)
To: brians@ucsd.edu; +Cc: pgsql-interfaces@hub.org
On Sat, 17 Oct 1998, Brian E. Sanders wrote:
> 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 someone knowledgeable would just tell me it's too esoteric a question for
> the mailing lists, please let me know and I'll look elsewhere.
I believe it's where a client can now abort a result while it's still
being received. It does this by sending an OOB (Out Of Band) packet to the
backend.
Peter
--
Peter T Mount peter@retep.org.uk
Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
Java PDF Generator: http://www.retep.org.uk/pdf
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: [INTERFACES] client connections to libpq
@ 1998-10-17 15:51 Tom Lane <tgl@sss.pgh.pa.us>
parent: Brian E. Sanders <brian@vingulf.org>
1 sibling, 0 replies; 3+ messages in thread
From: Tom Lane @ 1998-10-17 15:51 UTC (permalink / raw)
To: brians@ucsd.edu; +Cc: pgsql-interfaces@hub.org
"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
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~1998-10-17 15:51 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1998-10-17 09:38 client connections to libpq Brian E. Sanders <brian@vingulf.org>
1998-10-17 13:54 ` Peter T Mount <peter@retep.org.uk>
1998-10-17 15:51 ` Tom Lane <tgl@sss.pgh.pa.us>
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