On Fri, Dec 5, 2014 at 3:49 PM, Josh Berkus <j...@agliodbs.com> wrote: > to enable core dumps on the production replicas because writing out the > 16GB of shared buffers they had took over 10 minutes in a test.
No one ever thinks it'll happen to them anyway - recommending enabling core dumps seems like a waste of time, since as Tom mentioned package managers shouldn't be expected to get on board with that plan. I think a zero overhead backtrace feature from within a SIGSEGV handler (with appropriate precautions around corrupt/exhausted call stacks) using glibc is the right thing here. Indeed, glibc does have infrastructure that can be used to get a backtrace [1], which is probably what we'd end up using, but even POSIX has infrastructure like sigaltstack(). It can be done. [1] https://www.gnu.org/software/libc/manual/html_node/Backtraces.html -- Peter Geoghegan -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
