From tbarnard@povn.com Wed Dec  27 16:34:50 2000
Received: from mail.povn.com (mail.povn.com [206.107.251.6])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBRGYoL27734
	for <pgsql-interfaces@postgresql.org>;
	Wed, 27 Dec 2000 11:34:50 -0500 (EST)
	(envelope-from tbarnard@povn.com)
Received: from dev1 [204.94.232.50] by mail.povn.com
	(SMTPD32-6.05) id AA1542990146; Wed, 27 Dec 2000 08:34:29 -0800
Message-ID: <002201c07022$fa575400$32e85ecc@hartcomm.com>
From: "Tim Barnard" <tbarnard@povn.com>
To: <pgsql-interfaces@postgresql.org>
Subject: PQsetnonblocking questions
Date: Wed, 27 Dec 2000 08:35:09 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001F_01C06FDF.EBE7C8C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-Archive-Number: 200012/225
X-Sequence-Number: 571

This is a multi-part message in MIME format.

------=_NextPart_000_001F_01C06FDF.EBE7C8C0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello everyone,

I'm running release 7.0.3 and discovered that the include file libpq-fe.h p=
rototypes 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 PQsetnonbloc=
king? I am using PQconsumeInput, PQsendQuery, PQisBusy and PQgetResult.

Tim
S.E. Mgr
Hartford Communications

------=_NextPart_000_001F_01C06FDF.EBE7C8C0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello everyone,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I'm running release 7.0.3 and discovered t=
hat the=20
include file libpq-fe.h prototypes PQsetnonblocking as follows: int=20
PQsetnonblocking(PGconn * conn, int arg)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;However, the documentation shows it =
as:=20
PQsetnonblocking(PGconn * conn).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Does nayone know what the extra argument "=
int arg"=20
is for? And as my C app is not using a select statement to wait, do I even =
need=20
to use PQsetnonblocking? I am using PQconsumeInput, PQsendQuery, PQisBusy a=
nd=20
PQgetResult.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Tim</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>S.E. Mgr</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Hartford Communications</FONT></DIV></BODY=
></HTML>

------=_NextPart_000_001F_01C06FDF.EBE7C8C0--




From tgl@sss.pgh.pa.us Wed Dec  27 17:10:53 2000
Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBRHArL31382
	for <pgsql-interfaces@postgresql.org>;
	Wed, 27 Dec 2000 12:10:53 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eBRHB8C07698;
	Wed, 27 Dec 2000 12:11:08 -0500 (EST)
To: "Tim Barnard" <tbarnard@povn.com>
cc: pgsql-interfaces@postgresql.org
Subject: Re: PQsetnonblocking questions 
In-reply-to: <002201c07022$fa575400$32e85ecc@hartcomm.com> 
References: <002201c07022$fa575400$32e85ecc@hartcomm.com>
Comments: In-reply-to "Tim Barnard" <tbarnard@povn.com>
	message dated "Wed, 27 Dec 2000 08:35:09 -0800"
Date: Wed, 27 Dec 2000 12:11:08 -0500
Message-ID: <7695.977937068@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200012/228
X-Sequence-Number: 574

"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