| From: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Radu Radutiu <rradutiu(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to debug "background worker "parallel worker" (PID 32152) was terminated by signal 11: Segmentation fault" |
| Date: | 2020-04-27 14:27:26 |
| Message-ID: | CAKYtNAr6C9Ym81rq=OUdxNsbVNBG-oA2dx9YrMhRkitOxscJ2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 27 Apr 2020 at 17:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Radu Radutiu <rradutiu(at)gmail(dot)com> writes:
> > Can you guide me how to debug postgresql crash?
>
> A stack trace would be pretty useful.
>
> https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
>
> regards, tom lane
>
>
If you have given "-c" option while starting the server, then as your
background worker(PID: 32152) crashed with segment fault so you should
have core dump for this inside data folder. Check that core.32152 is
exist inside your data folder or not. If exists, then fire "gdb
postgres data/core.32152" and then "bt" to get stack trace.
--
Thanks and Regards
Mahendra Singh Thalor
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias Apitz | 2020-04-28 08:10:18 | Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;' |
| Previous Message | Tom Lane | 2020-04-27 13:58:54 | Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;' |