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

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Walker <r(dot)walker(at)mtcworldwide(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4635: postgres.exe crash when RAISE NOTICE during debugging of PL/pgSQL function in PgAdminIII
Date: 2009-02-04 20:31:06
Message-ID: 937d27e10902041231ua27251bp3e25643a6070e6b1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Feb 2, 2009 at 8:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Robert Walker" <r(dot)walker(at)mtcworldwide(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Eduard Deacoon 2009-02-05 07:51:55 BUG #4640: Drop leading zero in EXECUTE
Previous Message Robert Haas 2009-02-04 19:44:51 Re: [HACKERS] BUG #4516: FOUND variable does not work after RETURN QUERY