Chris Curvey <chris@chriscurvey.com> writes:
> in reverse order: no third-party, no contrib, no home-brew C. here is a
> stack trace from a fresh build of 9.1 beta 1 built with enable-cassert.
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000744777 in AllocSetAlloc (context=0x13f6d08, size=16) at
> aset.c:639
> 639 Assert(chunk->size >= size);
> #0 0x0000000000744777 in AllocSetAlloc (context=0x13f6d08, size=16) at
> aset.c:639
Hmm, that's pretty interesting. Possibly it's just another
manifestation of something scribbling past the end of its allocated
chunk, but my credence for that theory is way down if there's no add-on
code involved. Does the postmaster log show any messages like
WARNING: detected write past chunk end in ...
before the crash?
regards, tom lane