| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Raphael Megzari <raphael(at)megzari(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: BUG #16665: Segmentation fault |
| Date: | 2020-11-06 14:41:36 |
| Message-ID: | 1570029.1604673696@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Raphael Megzari <raphael(at)megzari(dot)com> writes:
> I have two questions
> - How can I make sure to have a postgres that includes debugging symbols?
(1) install the associated debug symbols package, or
(2) build from source and use --enable-debug configure option.
> - How can I verify after that my version includes debugging symbols?
You could attach to a running backend process with gdb and see whether
"bt full" gives you more than minimal output.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-11-06 14:49:58 | Re: BUG #16705: Triggers deferred during commit callback are not executed |
| Previous Message | Andrew Bille | 2020-11-06 14:28:09 | Re: BUG #16703: pg-dump fails to process recursive view definition |