Received: from berlin.atlantic.net (berlin.atlantic.net [209.208.0.20]) by hub.org (8.9.3/8.9.3) with ESMTP id VAA54594 for ; Mon, 17 May 1999 21:40:00 -0400 (EDT) (envelope-from jfd@mercury.net) Received: from rio.atlantic.net (rio.atlantic.net [209.208.0.4]) by berlin.atlantic.net (8.8.7/8.8.5) with ESMTP id VAA23557 for ; Mon, 17 May 1999 21:39:56 -0400 Received: from mercury.net (ocalfl-as-2-ip-32.atlantic.net [209.208.46.96]) by rio.atlantic.net (8.8.7/8.8.7) with ESMTP id VAA18515 for ; Mon, 17 May 1999 21:39:54 -0400 Sender: jfd@rio.atlantic.net Message-ID: <3740C4E8.AEA10070@mercury.net> Date: Mon, 17 May 1999 21:39:52 -0400 From: Jim Dossey X-Mailer: Mozilla 4.08 [en] (X11; I; UnixWare 5 i386) MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: libpq: checking for record locks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I'm trying to convert an existing application to postgresql 6.5. I'm using 6.5 because we need the "FOR UPDATE" clause in the SELECT statement. This is an interactive application and files locks would not be acceptable. I would like to find a way to detect if PQexec() or PQsendQuery() on a "SELECT ... FOR UPDATE" command are blocked because one or more if the records we are trying to select are locked by other transactions. I don't want the users waiting on a SELECT when the records they want are in use by another user, and we don't know when they will be freed. Thanks for any and all help, -- ----------------------------------------------------------------------- Jim Dossey mailto:jfd@mercury.net