Re: BUG #4635: postgres.exe crash when RAISE NOTICE during debugging of PL/pgSQL function in PgAdminIII - Mailing list pgsql-bugs

From Dave Page
Subject Re: BUG #4635: postgres.exe crash when RAISE NOTICE during debugging of PL/pgSQL function in PgAdminIII
Date
Msg-id 937d27e10902041231ua27251bp3e25643a6070e6b1@mail.gmail.com
Whole thread Raw
In response to Re: BUG #4635: postgres.exe crash when RAISE NOTICE during debugging of PL/pgSQL function in PgAdminIII  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Mon, Feb 2, 2009 at 8:46 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Robert Walker" <r.walker@mtcworldwide.com> writes:
>> I have a function that basically loops through a query and uses the results
>> from that query to do an individual insert into another table, and if there
>> is a unique violation, it simply raises a notice and continues on. When
>> trying to debug the function within PgAdminIII 1.8.4, when stepping through
>> to the point of the RAISE NOTICE statement, it displays the following and
>> then Windows informs me that postgres.exe has crashed:
>
> I suppose this is a bug in the plpgsql debugger; which you'll need to
> report to EDB.  The core postgres project does not maintain that code.

For info; this issue has been tracked down and a patch is being
prepared. It'll be in the 8.3.7 installers (unfortunately it's too
late for 8.3.6). I'll probably be able to provide updated DLLs in the
meantime.


--
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] BUG #4516: FOUND variable does not work after RETURN QUERY
Next
From: "Eduard Deacoon"
Date:
Subject: BUG #4640: Drop leading zero in EXECUTE