Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 6E6439FA075 for ; Sun, 28 Oct 2007 04:46:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 92874-04 for ; Sun, 28 Oct 2007 04:46:37 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from mail2007.strasbourg.4js.com (mail2007.strasbourg.4js.com [84.14.60.197]) by postgresql.org (Postfix) with ESMTP id A56EC9FA072 for ; Sun, 28 Oct 2007 04:46:36 -0300 (ADT) Received: from [10.0.0.196] (AStrasbourg-156-1-150-111.w90-13.abo.wanadoo.fr [90.13.125.111]) (authenticated bits=0) by mail2007.strasbourg.4js.com (8.13.8/8.13.8/Debian-3) with ESMTP id l9S7kSpi016848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 28 Oct 2007 08:46:30 +0100 Message-ID: <47243E0C.1070804@4js.com> Date: Sun, 28 Oct 2007 08:45:16 +0100 From: Sebastien FLAESCH Organization: Four J's Development Tools User-Agent: Thunderbird 1.5.0.9 (X11/20061220) MIME-Version: 1.0 To: "Florian G. Pflug" CC: Tom Lane , Heikki Linnakangas , pgsql-hackers@postgresql.org, Guillaume ERGAND Subject: Re: PostgreSQL 8.3, libpq and WHERE CURRENT OF 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> In-Reply-To: <472369E9.1050808@phlo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4613/Sun Oct 28 07:28:49 2007 on mail2007.strasbourg.4js.com X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/1412 X-Sequence-Number: 109780 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 >