From: Sebastien FLAESCH <sf@4js.com>
To: Florian G. Pflug <fgp@phlo.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org, Guillaume ERGAND <ger@4js.com>
Subject: Re: PostgreSQL 8.3, libpq and WHERE CURRENT OF
Date: Sun, 28 Oct 2007 08:45:16 +0100
Message-ID: <47243E0C.1070804@4js.com> (raw)
In-Reply-To: <472369E9.1050808@phlo.org>
References: <4721BAFE.3080601@4js.com>
<4721BF34.80901@enterprisedb.com>
<4721DECF.80401@4js.com>
<10801.1193404182@sss.pgh.pa.us>
<4721F289.7080800@4js.com>
<4721F33F.10704@4js.com>
<472369E9.1050808@phlo.org>
Just found this in the doc:
"WITH HOLD may not be specified when the query includes FOR UPDATE or FOR SHARE"
Here is what the Informix doc says about WITH HOLD + FOR UPDATE:
"It is possible to declare an update cursor with the WITH HOLD keywords,
but the only reason to do so is to break a long series of updates into
smaller transactions. You must fetch and update a particular row in the
same transaction."
However, I believe Informix keeps the locks set by WITH HOLD + FOR UPDATE
cursors, even if a transaction is terminated... locks are released when
the cursor is closed.
Seb
Florian G. Pflug wrote:
> Sebastien FLAESCH wrote:
>> Forget this one, just missing the WITH HOLD option... Must teach
>> myself a bit
>> more before sending further mails. Seb
>
> AFAIK you cannot use "WITH HOLD" together with updateable cursors.
> I might be wrong, though...
>
> regards, Florian Pflug
>
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-hackers@postgresql.org
Cc: sf@4js.com, fgp@phlo.org, tgl@sss.pgh.pa.us, heikki@enterprisedb.com, ger@4js.com
Subject: Re: PostgreSQL 8.3, libpq and WHERE CURRENT OF
In-Reply-To: <47243E0C.1070804@4js.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