From: Terry Lee Tucker <terry@esc1.com>
To: pgsql-interfaces@postgresql.org
Subject: Locking Question
Date: Thu, 10 Jun 2004 14:09:13 -0400
Message-ID: <200406101409.13547.terry@esc1.com> (raw)
Good Day,
I'm working on a transportation application which is written in C using
X-Windows. I've been experiementing with various methods for row level
locking. This application will be used by about 70 people at once with many
updates occurring to much of the data. At present, I'm looking at serialized
transactions. I have discovered that if the interface runs into a record that
is currently being updated with a SELECT FOR UPDATE, it sits and waits. I'm
looking for a way to get feedback to the user. I'm executing the SELECT FOR
UPDATE with a PQexec. PQexec blocks and waits. If I use PQsendQuery to
execute the statement, will I be able to get some sort of feed back from that
as to what is going on?
--
Quote: 35
"Losing [the debate about marriage] means losing marriage as a social
institution, a shared public norm. The question is not whether this
is a battle we can win, but whether it is a battle we can afford to
lose."
--Maggie Gallagher
Work: 1-336-372-6812
Cell: 1-336-363-4719
email: terry@esc1.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: terry@esc1.com
Subject: Re: Locking Question
In-Reply-To: <200406101409.13547.terry@esc1.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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