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 f4LEHqA36738 for ; Mon, 21 May 2001 10:17:53 -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 f4LEGjR25033; Mon, 21 May 2001 10:16:45 -0400 (EDT) To: Jan Wieck cc: Richard Huxton , Bruno Boettcher , pgsql-sql@postgresql.org Subject: Re: HELP: what's wrong with my PL/PSQL function?? In-reply-to: <200105211248.IAA01695@jupiter.jw.home> References: <200105211248.IAA01695@jupiter.jw.home> Comments: In-reply-to Jan Wieck message dated "Mon, 21 May 2001 08:48:23 -0400" Date: Mon, 21 May 2001 10:16:45 -0400 Message-ID: <25030.990454605@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/227 X-Sequence-Number: 3044 Jan Wieck writes: > Tom Lane wrote: >> I am not sure why this precious info is so deeply buried. I know why >> it's not part of the ERROR itself: our elog mechanism doesn't support >> that. But seems like it could at least be made a NOTICE rather than a >> DEBUG message. > Because at the time the NOTICE will be sent, the client > already received the ERROR and doesn't read from the > connection until the next command. So at least you'd have to > send an empty query to get it. Au contraire. To test this, I changed elog(DEBUG)s to elog(NOTICE)s in pl_exec.c, and now I get: regression=# select zz(); NOTICE: Last error occured while executing PL/pgSQL function zz NOTICE: line 2 at SQL statement ERROR: parser: parse error at or near "x" regression=# The reason is that libpq doesn't report query done until it gets the trailing 'Z' (ReadyForQuery) message, and the notices will come out before that. You might need to reword the notices a bit because they will appear before the error itself, but this still seems to me a lot better than having to go digging in the postmaster log (if there is one). regards, tom lane