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 f1KHb0x36089 for ; Tue, 20 Feb 2001 12:37:00 -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 f1KHaq915774; Tue, 20 Feb 2001 12:36:52 -0500 (EST) To: josh@agliodbs.com cc: sqllist , Jan Wieck Subject: Re: Huh? Mysterious Function Error In-reply-to: <3A92A15E.1E7DF00D@agliodbs.com> References: <3A92A15E.1E7DF00D@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Tue, 20 Feb 2001 08:54:54 -0800" Date: Tue, 20 Feb 2001 12:36:52 -0500 Message-ID: <15771.982690612@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/313 X-Sequence-Number: 1509 Josh Berkus writes: > ERROR: unexpected SELECT query in exec_stmt_execsql() plpgsql doesn't think you should execute bare SELECTs, only SELECT INTO. On reflection this seems an overly anal-retentive restriction, since there are cases where one might execute a SELECT for its side effects alone ("SELECT setval()" comes to mind). Jan, do you think there's a good case for refusing plain SELECTs? regards, tom lane