Re: Unexpected result from ALTER FUNCTION— looks like a bug - Mailing list pgsql-general

From Tom Lane
Subject Re: Unexpected result from ALTER FUNCTION— looks like a bug
Date
Msg-id 2713499.1650423990@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unexpected result from ALTER FUNCTION— looks like a bug  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: Unexpected result from ALTER FUNCTION— looks like a bug
List pgsql-general
Julien Rouhaud <rjuju123@gmail.com> writes:
> On Wed, Apr 20, 2022 at 10:47:07AM +0800, Julien Rouhaud wrote:
>> 
>> AFAICT the problem is that SET / RESET part is messing with the
>> HeapTuple, so you can't use the procForm reference afterwards.  Simply
>> processing parallel_item before set_items fixes the problem, as in the
>> attached.

> This time with the file.

Yeah, I arrived at the same fix.  Another possibility would be to
make the procForm pointer valid again after heap_modify_tuple,
but that seemed like it'd add more code for no really good reason.

            regards, tom lane



pgsql-general by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Unexpected result from ALTER FUNCTION— looks like a bug
Next
From: Julien Rouhaud
Date:
Subject: Re: Unexpected result from ALTER FUNCTION— looks like a bug