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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert Walker" <r(dot)walker(at)mtcworldwide(dot)com>
Cc: 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-02 20:46:24
Message-ID: 1559.1233607584@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message chetan 2009-02-03 09:24:32 BUG #4637: FATAL: sorry, too many clients already
Previous Message Pavel Stehule 2009-02-02 20:27:51 Re: BUG #4629: PL/pgSQL issue