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 f17KbBx00414 for ; Wed, 7 Feb 2001 15:37:12 -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 f17Kb7909963; Wed, 7 Feb 2001 15:37:08 -0500 (EST) To: Jeff Eckermann cc: "'pgsql-sql@postgresql.org'" Subject: Re: Use of RETURN in pl/pgsql function In-reply-to: <08CD1781F85AD4118E0800A0C9B8580B0948FF@NEZU> References: <08CD1781F85AD4118E0800A0C9B8580B0948FF@NEZU> Comments: In-reply-to Jeff Eckermann message dated "Wed, 07 Feb 2001 14:16:46 -0600" Date: Wed, 07 Feb 2001 15:37:07 -0500 Message-ID: <9960.981578227@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/139 X-Sequence-Number: 1319 Jeff Eckermann writes: > I'll be hornswoggled: that works. > I hadn't expected a problem, simply because I knew the range in advance: Odd. Maybe there is a compile-time, rather than run-time, check in plpgsql for falling off the end without a RETURN? I haven't looked ... regards, tom lane