| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rick Otten <rottenwindfish(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: signal 11 segfaults with parallel workers |
| Date: | 2017-07-28 00:48:24 |
| Message-ID: | 13841.1501202904@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Rick Otten <rottenwindfish(at)gmail(dot)com> writes:
> Is enabling DEBUG in the postgresql.conf sufficient to enable debug symbols
> in the core, or do I have to rebuild the postgresql binaries to get that?
You would need to recompile (with --enable-debug added to configure
switches) if they're not there already. But if you used somebody's
packaging rather than a homebrew build, you can probably get the
symbols installed without doing your own build.
> Is the core of any use without debug symbols enabled?
You should still be able to get a stack trace out of it, but the trace
would be much more informative with debug symbols. See
https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rick Otten | 2017-07-28 00:54:31 | Re: signal 11 segfaults with parallel workers |
| Previous Message | Rick Otten | 2017-07-28 00:43:50 | Re: signal 11 segfaults with parallel workers |