Re: [HACKERS] IndexBuild Function call fcinfo cannot access memory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] IndexBuild Function call fcinfo cannot access memory
Date
Msg-id 784.1485205204@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] IndexBuild Function call fcinfo cannot access memory  (Jia Yu <jiayu198910@gmail.com>)
Responses Re: [HACKERS] IndexBuild Function call fcinfo cannot access memory  (Jia Yu <jiayu198910@gmail.com>)
List pgsql-hackers
Jia Yu <jiayu198910@gmail.com> writes:
> However, these methods don't work in the normal PG server. It gave me
> "segmentation fault"
> ...
> Here is my backtrace. It looks like I cannot access fcinfo. Can you help me
> about this? Or just some hints? I have been struggling with this problem
> for weeks.

What's the problematic line (hippo.c:154) doing?  What's before
that in the hippobuild function?

I wouldn't put much stock in the "Cannot access memory" message ... that
just means gdb is confused, which it frequently is.  But possibly
building with -O0 would make it less confused.

BTW, I gather from the reference to OidFunctionCall3Coll that you're
using PG 9.5 or older.  It'd be a good idea to switch to 9.6, which has
noticeably cleaner indexam APIs that allow some compiler error checking
on those calls.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan
Next
From: Corey Huinker
Date:
Subject: Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)