| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kamil Jońca <kjonca(at)fastmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Random crashes - segmentation fault |
| Date: | 2019-12-17 04:59:20 |
| Message-ID: | 20191217045920.GJ2344@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Fri, Dec 13, 2019 at 04:05:34PM +0100, Kamil Jońca wrote:
> Today server crashed again.
> --8<---------------cut here---------------start------------->8---
> 2019-12-13 15:41:38 CET DEBUG: starting background worker process
> "parallel worker for PID 364516"
> TRAP: FailedAssertion("!(result->tdrefcount == -1)", File:
> /build/postgresql-12-123lrX/postgresql-12-12.1/build/../src/backend/utils/cache/typcache.c",
> Line: 2621)
> --8<---------------cut here---------------end--------------->8---
>
> I have core dump.
Could it be possible to see a full backtrace then? Using gdb that
would mean to use "bt" to print the full stack. What kind of function
is get_free_numbers() actually and what does it do?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | avinash varma | 2019-12-17 06:11:22 | Re: Planning time is high in Postgres 11.5 Compared with Postgres 10.11 |
| Previous Message | Alexander Lakhin | 2019-12-17 03:00:00 | Re: BUG #16161: pg_ctl stop fails sometimes (on Windows) |