pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedPQsetnonblocking questions
2+ messages / 2 participants
[nested] [flat]
* PQsetnonblocking questions
@ 2000-12-27 16:35 Tim Barnard <tbarnard@povn.com>
0 siblings, 1 reply; 2+ messages in thread
From: Tim Barnard @ 2000-12-27 16:35 UTC (permalink / raw)
To: pgsql-interfaces
Hello everyone,
I'm running release 7.0.3 and discovered that the include file libpq-fe.h prototypes PQsetnonblocking as follows: int PQsetnonblocking(PGconn * conn, int arg)
However, the documentation shows it as: PQsetnonblocking(PGconn * conn).
Does nayone know what the extra argument "int arg" is for? And as my C app is not using a select statement to wait, do I even need to use PQsetnonblocking? I am using PQconsumeInput, PQsendQuery, PQisBusy and PQgetResult.
Tim
S.E. Mgr
Hartford Communications
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: PQsetnonblocking questions
@ 2000-12-27 17:11 Tom Lane <tgl@sss.pgh.pa.us>
parent: Tim Barnard <tbarnard@povn.com>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2000-12-27 17:11 UTC (permalink / raw)
To: Tim Barnard <tbarnard@povn.com>; +Cc: pgsql-interfaces
"Tim Barnard" <tbarnard@povn.com> writes:
> ... do I even need to use PQsetnonblocking?
Not unless you are unhappy about the possibility of short-term blocking
during PQsendQuery (which is a very remote possibility anyway, unless
you send huge query strings).
I believe that the nonblocking-mode code is pretty buggy, and don't
recommend using it unless you really need it and want to help debug
it...
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2000-12-27 17:11 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-12-27 16:35 PQsetnonblocking questions Tim Barnard <tbarnard@povn.com>
2000-12-27 17:11 ` 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