On 2015-02-14 13:29, Stuart Henderson wrote: > 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). >
Yup, backward memcpy it is (from /var/log/messages): Feb 14 12:27:34 elysion postgres: backwards memcpy Feb 14 12:28:10 elysion last message repeated 8 times Feb 14 12:30:19 elysion last message repeated 28 times Feb 14 12:40:28 elysion last message repeated 128 times Feb 14 12:50:40 elysion last message repeated 128 times Feb 14 13:00:41 elysion last message repeated 126 times Feb 14 13:10:42 elysion last message repeated 128 times Feb 14 13:20:49 elysion last message repeated 126 times Feb 14 13:30:55 elysion last message repeated 128 times Feb 14 13:41:06 elysion last message repeated 132 times Feb 14 13:51:10 elysion last message repeated 128 times Feb 14 14:01:18 elysion last message repeated 128 times Feb 14 14:08:18 elysion last message repeated 91 times Am I mistaken in understanding that this is an issue with postgresql itself, and not a local configuration error? I tried building postgres with debug symbols (I added the flags described here[1] to the ports Makefile), but the backtrace is still useless: # sudo -u _postgresql gdb -q -c postgres.core /usr/local/bin/postgres Core was generated by `postgres'. Program terminated with signal 6, Aborted. Loaded symbols for /usr/local/bin/postgres #0 0x00000bd73424292a in ?? () (gdb) bt #0 0x00000bd73424292a in ?? () #1 0x0000000000000000 in ?? () Do I need any further OpenBSD-specific changes to get a useful backtrace? (I've to admit that I'm too familiar with debuging with gdb on any platform). Thanks for all the feedback so far! [1]: https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQ L_backend_on_Linux/BSD#Debugging_the_core_dump_-_example -- Hugo Osvaldo Barrera A: Because we read from top to bottom, left to right. Q: Why should I start my reply below the quoted text? [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]