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: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 10:57:25
Message-ID: 937d27e10902270257s8336f0eu2898768c50dbd5e0@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Feb 27, 2009 at 10:37 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message aiwaniuk 2009-02-27 11:00:18 Re: BUG #4677: memory growth
Previous Message Denis Afonin 2009-02-27 10:40:44 BUG #4680: Server crashed if using wrong (mismatch) conversion functions