| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jia Yu <jiayu198910(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: IndexBuild Function call fcinfo cannot access memory |
| Date: | 2017-01-23 21:00:04 |
| Message-ID: | 784.1485205204@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jia Yu <jiayu198910(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Corey Huinker | 2017-01-23 21:12:36 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | Jim Nasby | 2017-01-23 20:59:32 | Re: PoC plpgsql - possibility to force custom or generic plan |