On 2015-02-14, Joel Sing <j...@sing.id.au> wrote: > The interesting/useful part is: > > LOG: statement: SELECT ... ORDER BY c.oid > LOG: server process (PID 11531) was terminated by signal 6: Abort trap > > So the server process is being sent a SIGABRT, which is causing it to > terminate. There is a good chance this this is coming from the stack > protector, which sends a SIGABRT if the stack is smashed.
Oh, good call. It could also be a backwards memcpy which would show up in /var/log/messages (assuming usual config). If it were another program, our strict mutex checks can also cause SIGABRT, but that won't apply to pgsql as it's not threaded.
