| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | David Kohn <djk447(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15036: Un-killable queries Hanging in BgWorkerShutdown |
| Date: | 2018-02-11 02:27:30 |
| Message-ID: | CAEepm=3-gmmBQX8C5NLvUd4=9M6GXKB7kZhbi4uAmfpcDqhfNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Feb 11, 2018 at 2:58 PM, David Kohn <djk447(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 許耀彰 | 2018-02-11 08:28:18 | postgresql data transfer from 9.3 to 9.4 |
| Previous Message | David Kohn | 2018-02-11 01:58:00 | Re: BUG #15036: Un-killable queries Hanging in BgWorkerShutdown |