X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9AD31D1B50B for ; Wed, 17 Sep 2003 21:23:37 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 99770-07 for ; Wed, 17 Sep 2003 18:23:06 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id E396AD1B4F1 for ; Wed, 17 Sep 2003 18:23:03 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h8HLN5pr006000; Wed, 17 Sep 2003 17:23:05 -0400 (EDT) To: miko@idocs.com (Miko O'Sullivan) Cc: pgsql-sql@postgresql.org Subject: Re: [BUGS] session variable In-reply-to: References: <200309032042.h83KgmJ24665@candle.pha.pa.us> Comments: In-reply-to miko@idocs.com (Miko O'Sullivan) message dated "13 Sep 2003 11:23:36 -0700" Date: Wed, 17 Sep 2003 17:23:05 -0400 Message-ID: <5999.1063833785@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/170 X-Sequence-Number: 15148 miko@idocs.com (Miko O'Sullivan) writes: > Unfortunately in the 7.2.x version I have available, EXECUTE does not > allow "select into". The docs suggests a technique for using a FOR > loop to extract information from an EXECUTE, but the technique only > works for finite set of expected variables, not for arbitrary values. How do you figure that? AFAICS "FOR" with a record variable as target will cover any case that SELECT INTO could handle. regards, tom lane