Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f18Jnpx34657; Thu, 8 Feb 2001 14:49:51 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f18JnQ912699; Thu, 8 Feb 2001 14:49:26 -0500 (EST) To: Peter Eisentraut cc: Jan Wieck , pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: PL/pgsql EXECUTE 'SELECT INTO ...' In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Thu, 08 Feb 2001 20:37:16 +0100" Date: Thu, 08 Feb 2001 14:49:26 -0500 Message-ID: <12696.981661766@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/283 X-Sequence-Number: 4414 Peter Eisentraut writes: > Tom Lane writes: >> I am inclined to keep our options open by forbidding EXECUTE 'SELECT >> INTO ...' for now. That's more than a tad annoying, because that leaves >> no useful way to do a dynamically-built SELECT, but if we don't forbid >> it I think we'll regret it later. > You can always use CREATE TABLE AS. Does SPI_exec() support that? (Tries it ... seems to work ...) Cool. OK, we have the bases covered then; there's no need to allow SELECT INTO inside EXECUTE until we can make it work as expected. regards, tom lane