On Sun, Feb 11, 2018 at 2:58 PM, David Kohn <djk447@gmail.com> wrote:
> I tried to get a stacktrace, but because nothing's crashing normal
> stacktraces don't happen, tried profiling with perf, sampling specifically
> the procs that are stuck, but because they're not doing anything there's no
> samples...so stacktrace not helping so much, thoughts on how to get around
> that?
You can get a backtrace from a running program with by connecting to
it with gdb -p PID, then bt for the backtrace. You might need to
install the symbols package if you only see addresses (on debianoid
systems postgresql-10-dbgsym, not sure what it's called on RHELish
systems).
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
--
Thomas Munro
http://www.enterprisedb.com