pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hamid Akhtar <hamid.akhtar@gmail.com>
Cc: johannes.mols@googlemail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
Date: Wed, 08 Apr 2020 10:10:59 -0400
Message-ID: <1650.1586355059@sss.pgh.pa.us> (raw)
In-Reply-To: <CANugjhtKxBCMhS8u9SX_DD66qhXBB11-pyxLGnG1QFG+o0+aag@mail.gmail.com>
References: <16351-5cac06fa29fc19e1@postgresql.org>
	<CANugjhtKxBCMhS8u9SX_DD66qhXBB11-pyxLGnG1QFG+o0+aag@mail.gmail.com>

Hamid Akhtar <hamid.akhtar@gmail.com> writes:
> Unfortunately, there isn't enough information here for anybody to reproduce
> the issue.

Yeah.  There is some info here about extracting a stack trace, which
could be quite helpful:

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

			regards, tom lane





view thread (11+ messages)  latest in thread

Message-ID: <1650.1586355059@sss.pgh.pa.us>
Permalink:  ../1650.1586355059@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1650.1586355059@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, hamid.akhtar@gmail.com, johannes.mols@googlemail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16351: PostgreSQL closing connection during requests with segmentation fault
  In-Reply-To: <1650.1586355059@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox