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

Re: PATCH: FB#15944: An error has occurred if debug function

From: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: FB#15944: An error has occurred if debug function
Date: 2010-06-08 06:17:38
Message-ID: AANLkTilmRF5lXxZZjoaJtC5gO-E6sUSULxeAwAhcbf5V@mail.gmail.com (view raw or flat)
Thread:
Lists: pgadmin-hackers
Hi Dave,

On Tue, Jun 8, 2010 at 1:20 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> On Mon, Jun 7, 2010 at 4:31 PM, Ashesh Vashi
> <ashesh(dot)vashi(at)enterprisedb(dot)com> wrote:
> > HI Dave,
> > Please find the patch for the same.
> > If plpgsql does have out parameter, it fails to debug.
> > This patch will apply on both trunk and REL-1_10_PATCHES branch.
>
> Hi Ashesh,
>
> Is that patch right? Surely we should never try to pass a value into
> an OUT parameter.
>
You're right.
We never ask for input from the user for the OUT parameter and the argument
value will always be NULL for these parameters. And hence, this patch worked
for me.

Please find the updated patch.

--
Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise Postgres Company<http://www.enterprisedb.com>

Attachment: FB15944.patch
Description: text/x-patch (540 bytes)

In response to

Responses

pgadmin-hackers by date

Next:From: Cousin FlorenceDate: 2010-06-08 09:17:40
Subject: Crash "The memory could not be read" on Windows XP
Previous:From: Dave PageDate: 2010-06-07 19:50:48
Subject: Re: PATCH: FB#15944: An error has occurred if debug function

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