Re: [SQL] PostgreSQL server terminated by signal 11

"Daniel Caune" <daniel(dot)caune(at)ubisoft(dot)com> writes:
> Program received signal SIGSEGV, Segmentation fault.
> 0x08079e2a in slot_attisnull ()
> (gdb) bt
> #0 0x08079e2a in slot_attisnull ()
> #1 0x0807a1d0 in slot_getattr ()
> #2 0x080c6c73 in FormIndexDatum ()
> #3 0x080c6ef1 in IndexBuildHeapScan ()
> #4 0x0809b44d in btbuild ()
> #5 0x0825dfdd in OidFunctionCall3 ()
> #6 0x080c4f95 in index_build ()
> #7 0x080c68eb in index_create ()
> #8 0x08117e36 in DefineIndex ()

Hmph. gdb is lying to you, because slot_getattr doesn't call slot_attisnull.
This isn't too unusual in a non-debug build, because the symbol table is
incomplete (no mention of non-global functions).

Given that this doesn't happen right away, but only after it's been
processing for awhile, we can assume that FormIndexDatum has been
successfully iterated many times already, which seems to eliminate
theories like the slot or the keycol value being bogus. I'm pretty well
convinced now that we're looking at a problem with corrupted data. Can
you do a SELECT * FROM (or COPY FROM) the table without error?

regards, tom lane