Skip site navigation (1) Skip section navigation (2)

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-27 09:39:05
Message-ID: 937d27e10902270139g2d0b48b7uec14041ac2e95b5c@mail.gmail.com (view raw or flat)
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.

We've tracked this issue down to what appears to be a pl/pgsql bug -
after setting state_var->value and errm_var->value to null,
state_var->isnull and errm_var->isnull are not set correspondingly.

This has been fixed in HEAD already - the attached patch is for 8.3.6
(and should probably be back-patched to at least 8.2).

Credit goes to Ashesh Vashi for tracking this down.

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

Attachment: plpgsql.diff
Description: application/octet-stream (563 bytes)

In response to

Responses

pgsql-bugs by date

Next:From: BhajeshDate: 2009-02-27 10:06:13
Subject: BUG #4679: invalid UTF-8 byte sequence detected near byte 0xa3 + postgresql
Previous:From: Harald Armin MassaDate: 2009-02-27 09:36:43
Subject: BUG #4678: codepage UTF8 crashes psql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group