From: | Jim Dossey <jfd(at)mercury(dot)net> |
---|---|
To: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | libpq: trying to detect record locks |
Date: | 1999-05-18 01:54:47 |
Message-ID: | 3740C867.39D903C1@mercury.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
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(at)mercury(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 1999-05-18 03:24:53 | Re: [INTERFACES] Vacuum takes for ever |
Previous Message | Jim Dossey | 1999-05-18 01:39:52 | libpq: checking for record locks |