Received: from ingenico.com.au (unknown [202.167.40.101]) by postgresql.org (Postfix) with ESMTP id D5393475484; Sun, 21 Apr 2002 22:16:43 -0400 (EDT) Message-ID: <005b01c1e9a3$c0a6ea30$660d090a@software.ingenico.com.au> From: "Nicolas Bazin" To: Cc: "Michael Meskes" Subject: implementation of SET LOCK MODE TO [WAIT [seconds] | NOT WAIT] for ecpq Date: Mon, 22 Apr 2002 12:16:46 +1000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0058_01C1E9F7.921F18F0" X-Archive-Number: 200204/38 X-Sequence-Number: 2580 This is a multi-part message in MIME format. ------=_NextPart_000_0058_01C1E9F7.921F18F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I need to avoid my process to wait for too long. This syntax is not support= ed by the BE so I thought I would modify ECPGexecute to use asynchronous fu= nctions instead of PQexec. The problem is the NOT WAIT mode which needs som= e sort of info from the BE to know whether the statement has immediatly sta= rted to be executed or is in a queue waiting for its turn. Any idea or comment on this feature? ------=_NextPart_000_0058_01C1E9F7.921F18F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I need to avoid my process to wait for too= long.=20 This syntax is not supported by the BE so I thought I would modify ECPGexec= ute=20 to use asynchronous functions instead of PQexec. The problem is the NOT WAI= T=20 mode which needs some sort of info from the BE to know whether the statemen= t has=20 immediatly started to be executed or is in a queue waiting for its=20 turn.
Any idea or comment on this feature?
 
------=_NextPart_000_0058_01C1E9F7.921F18F0--