Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fB3JN9m16588 for ; Mon, 3 Dec 2001 14:23:09 -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.4/8.11.4) with ESMTP id fB3JN8i18425; Mon, 3 Dec 2001 14:23:08 -0500 (EST) To: ananthreddy@yahoo.com (ananth) cc: pgsql-sql@postgresql.org Subject: Re: Error in executing plpgsql function In-reply-to: <5304e92b.0111302223.5e89b405@posting.google.com> References: <5304e92b.0111302223.5e89b405@posting.google.com> Comments: In-reply-to ananthreddy@yahoo.com (ananth) message dated "30 Nov 2001 22:23:35 -0800" Date: Mon, 03 Dec 2001 14:23:07 -0500 Message-ID: <18422.1007407387@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200112/31 X-Sequence-Number: 5854 ananthreddy@yahoo.com (ananth) writes: > The problem is when I run this function by passing a parameter values > where row does not exist in table. I expect it to print message and > return false. Instead it disconnects from server and throughs lot of > errors in log file. Here is output from executing this function What PG version are you running? I seem to recall that there was a bug with some not-found cases in plpgsql a while back. If you're not using 7.1.3, update. regards, tom lane