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

On Mon, Jun 7, 2010 at 4:31 PM, Ashesh Vashi
<ashesh.vashi@enterprisedb.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.


--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company

On Tue, Jun 8, 2010 at 7:17 AM, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Dave,
>
> On Tue, Jun 8, 2010 at 1:20 AM, Dave Page <dpage@pgadmin.org> wrote:
>>
>> On Mon, Jun 7, 2010 at 4:31 PM, Ashesh Vashi
>> <ashesh.vashi@enterprisedb.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 - patch applied.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company