pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: piotrwlodarczyk89@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16184: Segmentation Fault during update
Date: Thu, 02 Jan 2020 10:33:15 -0500
Message-ID: <17312.1577979195@sss.pgh.pa.us> (raw)
In-Reply-To: <16184-2f718844be10c863@postgresql.org>
References: <16184-2f718844be10c863@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> writes:
> Log:
> 2020-01-02 15:42:26 CET [12729]: [95-1] user=,db=,xid=0,state=00000 LOG: 
> server process (PID 28879) was terminated by signal 11: Segmentation fault
> 2020-01-02 15:42:26 CET [12729]: [96-1] user=,db=,xid=0,state=00000 DETAIL: 
> Failed process was running: UPDATE job_abstract a
>           SET job_status = job_status
>           WHERE (a.xmax :: TEXT :: BIGINT < (SELECT
> txid_snapshot_xmin(txid_current_snapshot()))) AND ((SELECT

Clearly a bug, but there's not much we can do with this amount of
information.  If you can provide a stack trace, that'd be helpful.

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

> Reproducting this bug is not easy and I don't know which conditions has to
> be met to replicate this bug. But during application is working and we made
> this update, segmentation fault occurs. But sometimes it works. 

My gut instinct is that this might be a concurrent-update problem,
which would explain the lack of reproducibility.  Try to get
multiple sessions to update the same table row(s) at the same time.

Also, we had some bugs of that ilk on 12.0, please make sure you
really are updated to 12.1.

			regards, tom lane





view thread (7+ messages)  latest in thread

Message-ID: <17312.1577979195@sss.pgh.pa.us>
Permalink:  ../17312.1577979195@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17312.1577979195@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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, piotrwlodarczyk89@gmail.com
  Subject: Re: BUG #16184: Segmentation Fault during update
  In-Reply-To: <17312.1577979195@sss.pgh.pa.us>
  References: <16184-2f718844be10c863@postgresql.org> <17312.1577979195@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