From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Johannes Mols <johannes(dot)mols(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hamid Akhtar <hamid(dot)akhtar(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault |
Date: | 2020-04-09 01:48:35 |
Message-ID: | 20200409014835.GN1606@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Apr 08, 2020 at 04:58:04PM +0200, Johannes Mols wrote:
> I've tried to that but I'm unfortunately struggling to install the debug
> symbols (https://wiki.ubuntu.com/DebuggingProgramCrash)
> I can't seem to figure out how to do this. Is there any guide that is
> easier to understand for someone who isn't crazy knowledgeable about Linux?
> I would really like to provide you with the information you need, I have no
> idea how to solve this myself and if it is a bug or if something went wrong
> on my end.
Did you try to install the debug symbols using the commands on the
wiki and what kind of failure did you see then? When it comes to
Ubuntu and Debian, there are a set of -debug RPMs which can be
installed to introduce all the debug symbols which are needed to get a
clear stack trace from a Postgres backend. Also, your bug report
mentions Postgres 10.12. Is that a new issue with this minor version?
Were things working as you expected with older versions?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2020-04-09 02:26:57 | Re: [BUG] non archived WAL removed during production crash recovery |
Previous Message | Fan Liu | 2020-04-09 01:45:52 | RE: why wal_max_size does not work? |