X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 313F8545B4 for ; Fri, 11 Mar 2005 18:54:46 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 36152-03 for ; Fri, 11 Mar 2005 18:54:36 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 425B5563DE for ; Fri, 11 Mar 2005 18:54:34 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2BIsXPZ004364; Fri, 11 Mar 2005 13:54:33 -0500 (EST) To: Kris Kiger Cc: "Pgsql-Admin (E-mail)" Subject: Re: Functions and transactions In-reply-to: <4231CBEE.60109@musicrebellion.com> References: <421CF15C.6010306@turtle-entertainment.de> <421CF1CE.3000800@turtle-entertainment.de> <422F6203.1090800@musicrebellion.com> <7701.1110407641@sss.pgh.pa.us> <42305968.10100@musicrebellion.com> <15242.1110469332@sss.pgh.pa.us> <4230A6AA.6030204@musicrebellion.com> <27098.1110499829@sss.pgh.pa.us> <4231CBEE.60109@musicrebellion.com> Comments: In-reply-to Kris Kiger message dated "Fri, 11 Mar 2005 11:48:46 -0500" Date: Fri, 11 Mar 2005 13:54:33 -0500 Message-ID: <4363.1110567273@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/189 X-Sequence-Number: 16687 Kris Kiger writes: > Interesting. That makes sense, though. So, is there a good way to lock > a set of rows using SELECT FOR UPDATE in plpgsql? I assume using > PERFORM would yield the same problem, because it immediately discards > the results. I think PERFORM would work. The fact that plpgsql ignores the results doesn't mean you don't have lock on the rows. regards, tom lane