Received: from sss.pgh.pa.us (sss.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3O0JI336318 for ; Mon, 23 Apr 2001 20:19:18 -0400 (EDT) (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.3/8.11.3) with ESMTP id f3O0JDR24462; Mon, 23 Apr 2001 20:19:13 -0400 (EDT) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: Problems handling errors in PL/pgSQL In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Mon, 23 Apr 2001 17:15:43 -0700" Date: Mon, 23 Apr 2001 20:19:13 -0400 Message-ID: <24459.988071553@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/362 X-Sequence-Number: 2720 "Josh Berkus" writes: > Always good to have you folks test something. This does appear to be a > bug ... in KPSQL (the KDE GUI for PSQL), not in Postgres. When I run it > through command-line PSQL, an error is returned; for some reason, KPSQL > returns the return value for the function and no error. But how would KPSQL know what value the function might have returned? Something fishy here ... did you check the postmaster log to see whether an error is really being reported or not? regards, tom lane