| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | kjonca(at)fastmail(dot)com (Kamil Jońca ) |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Random crashes - segmentation fault |
| Date: | 2019-11-13 15:07:03 |
| Message-ID: | 6161.1573657623@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
kjonca(at)fastmail(dot)com (Kamil =?iso-8859-2?Q?Jo=F1ca?=) writes:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>> Could it be possible to see a backtrace of the crash? There is
> Erm. Only thing I can do is to configure for debug future crashes. Could you
> tell me what and how to configure to get backtrace?
There's some accumulated wisdom at
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
I'd suggest that before worrying about that, you should install 12.1
(official release is tomorrow) and see if the crashes go away. There's
not much info in this report, but it could match any of several
already-fixed bugs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-11-13 15:18:03 | Re: 回复： 回复： BUG #16101: tables in the DB is not available after pg_restore |
| Previous Message | Tom Lane | 2019-11-13 15:00:23 | Re: 回复： BUG #16101: tables in the DB is not available after pg_restore |