Re: 11beta crash/assert caused by parameter type changes
Vik Fearing <vik.fearing@2ndquadrant.com>
From: Vik Fearing <vik.fearing@2ndquadrant.com>
To: Andrew Gierth <andrew@tao11.riddles.org.uk>, pgsql-hackers@postgresql.org
Date: 2018-07-24T21:34:15Z
Lists: pgsql-hackers
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. -- Vik Fearing +33 6 46 75 15 36 http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
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