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 937d27e10902270257s8336f0eu2898768c50dbd5e0@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  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
On Fri, Feb 27, 2009 at 10:37 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:

> But I wonder, why does plpgsql debugger even try to display those variables
> after the exception block? I'm not familiar with the tool; I'm guessing that
> it just displays all variables, regardless of scope.

I believe so. I'm not that familiar with the plugin code.

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

pgsql-bugs by date:

Previous
From: "Denis Afonin"
Date:
Subject: BUG #4680: Server crashed if using wrong (mismatch) conversion functions
Next
From: aiwaniuk@instytut.com.pl
Date:
Subject: Re: BUG #4677: memory growth