Re: [HACKERS] `array_position...()` causes SIGSEGV

2016-12-09 Thread Alvaro Herrera
Junseok Yang wrote: > Hello hackers, > > I met SIGSEGV when using `array_position()` with record type > arguments, so I've written a patch which corrects this problem. It > seems that `array_position...()` sets wrong memory context for the > cached function (in this case `record_eq()`) which is us

Re: [HACKERS] `array_position...()` causes SIGSEGV

2016-12-09 Thread Alvaro Herrera
Michael Paquier wrote: > On Fri, Dec 9, 2016 at 3:14 PM, Junseok Yang wrote: > > I met SIGSEGV when using `array_position()` with record type > > arguments, so I've written a patch which corrects this problem. It > > seems that `array_position...()` sets wrong memory context for the > > cached fun

Re: [HACKERS] `array_position...()` causes SIGSEGV

2016-12-08 Thread Michael Paquier
On Fri, Dec 9, 2016 at 3:14 PM, Junseok Yang wrote: > I met SIGSEGV when using `array_position()` with record type > arguments, so I've written a patch which corrects this problem. It > seems that `array_position...()` sets wrong memory context for the > cached function (in this case `record_eq()`

[HACKERS] `array_position...()` causes SIGSEGV

2016-12-08 Thread Junseok Yang
Hello hackers, I met SIGSEGV when using `array_position()` with record type arguments, so I've written a patch which corrects this problem. It seems that `array_position...()` sets wrong memory context for the cached function (in this case `record_eq()`) which is used to find a matching element.