Re: Fast default stuff versus pg_upgrade
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@lists.postgresql.org
Date: 2018-06-20T02:46:24Z
Lists: pgsql-hackers
On 2018-06-19 22:41:26 -0400, Andrew Dunstan wrote: > This unfortunately crashes and burns if we use DirectFunctionCall3 to call > array_in, because it uses fn_extra. There is the CallerFInfoFunctionCall > stuff, but it only has 1 and 2 arg variants, and array_in takes 3. In > retrospect we should probably have added a 3 arg form - quite a few input > functions take 3 args. Anything else is likely to be rather uglier. > > Attaching the failing patch. I'll attack this again in the morning. Why don't you just use OidFunctionCall3? Or simply an explicit fmgr_info(), InitFunctionCallInfoData(), FunctionCallInvoke() combo? Greetings, Andres Freund
Commits
-
Allow for pg_upgrade of attributes with missing values
- 2448adf29c54 11.0 landed