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

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Vik Fearing <vik.fearing@2ndquadrant.com>

Cc: Andrew Gierth <andrew@tao11.riddles.org.uk>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>

Date: 2018-07-26T14:19:15Z

Lists: pgsql-hackers

On Tue, Jul 24, 2018 at 5:34 PM, Vik Fearing
<vik.fearing@2ndquadrant.com> wrote:
> On 24/07/18 22:50, Andrew Gierth wrote:
>> Haven't had time yet to poke at what's changed in detail.
>
> git bisect lays the blame on 6719b238e8f0ea83c39d2b1728c7670cdaa34e06.

Sounds like an open item for Tom, then.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

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