Received: from localhost (unknown [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 1437F9FA4AE for ; Sun, 28 Oct 2007 04:29:50 -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 86143-05 for ; Sun, 28 Oct 2007 04:29:47 -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 81C3D9F9CA9 for ; Sun, 28 Oct 2007 04:29:46 -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 l9S7TV4E016512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 28 Oct 2007 08:29:37 +0100 Message-ID: <47243A13.70607@4js.com> Date: Sun, 28 Oct 2007 08:28:19 +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/4612/Sun Oct 28 06:51:54 2007 on mail2007.strasbourg.4js.com X-Virus-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/1411 X-Sequence-Number: 109779 Florian, Do you mean WITH HOLD cursors (+ FOR UPDATE) can also be used to do DELETE/UPDATE WHERE CURRENT OF (i.e. outside transactions) ? From my experience this is an Informix-only feature, but if PostgreSQL supports that it would help a lot to migrate existing applications. I understand it's not a usual feature - one typically SELECT FOR UPDATE and DELETE / UPDATE WHERE CURRENT OF in a transaction block. I will give it a try anyway. Further, I was wondering if DECLARE CURSOR could be slower as plain SELECT statements. I will see this rapidly anyway so if someone can give me some tips about the overhead/cost of moving to DECLARE CURSOR, it would help me a lot. Remember I am talking about a driver for our VM = moving to DECLARE CURSOR would apply to all SELECT statements used in an application. Thanks 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 >