Re: segfault when creating index on huge table

Hi Tom,

Thanks for your reply!

I’m having trouble getting the full stack trace since it’s a controlled environment and I need to figure out a way to install all the debug info packages.

but for now i have checked all core dumps which all seems crashed at same point.

warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffe2b31000
Core was generated by `postgres: osm osm_planet [local] ALTER TABLE '.
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000785180 in med3_tuple (a=0x7f31613f1028, b=0x7f31613f1040, c=0xffffffff3ffffffd, cmp_tuple=0x7f43613f1010, state=0x1) at qsort_tuple.c:66
66 {
Missing separate debuginfos, use: debuginfo-install glibc-2.12-1.149.el6_6.5.x86_64

I’ll try get help to get a full stack trace and post here as soon as possible.

Thanks
Yiqing

> On Jul 16, 2015, at 11:14 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Yiqing Jin <yiqing(dot)jin(at)gmail(dot)com> writes:
>> I'm trapped with a problem when trying to create an index on a table with
>> about 2.8 billion records in it.
>> ALTER TABLE ONLY nodes ADD CONSTRAINT pk_nodes PRIMARY KEY (id);
>> or
>> create index pknode on nodes(id);
>
>> Postgres terminated with segfault during the proocess.
>
> That shouldn't happen. Can you get a stack trace from the core dump?
>
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
>
> regards, tom lane