Horton

Re: Unexpected result from ALTER FUNCTION— looks like a bug

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Bryn Llewellyn <bryn@yugabyte.com>, pgsql-general list <pgsql-general@lists.postgresql.org>
Date: 2022-04-20T03:06:30Z
Lists: 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

Commits

  1. Fix breakage in AlterFunction().