Re: 11beta crash/assert caused by parameter type changes

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

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

To: Robert Haas <robertmhaas@gmail.com>

Cc: Vik Fearing <vik.fearing@2ndquadrant.com>, Andrew Gierth <andrew@tao11.riddles.org.uk>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2018-07-26T14:28:12Z

Lists: pgsql-hackers

Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Jul 24, 2018 at 5:34 PM, Vik Fearing
> <vik.fearing@2ndquadrant.com> wrote:
>> git bisect lays the blame on 6719b238e8f0ea83c39d2b1728c7670cdaa34e06.

> Sounds like an open item for Tom, then.

Yeah, agreed, but I've not had time for it yet.

			regards, tom lane

Commits

Provide plpgsql tests for cases involving record field changes.
- c606f10ff832 11.0 landed
- 9f77ad2672f1 12.0 landed
Avoid crash in eval_const_expressions if a Param's type changes.
- 9207a64e1496 11.0 landed
- 662d12aea1d6 12.0 landed
Rearrange execution of PARAM_EXTERN Params for plpgsql's benefit.
- 6719b238e8f0 11.0 cited