Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1in2TX-0006yx-DN for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Jan 2020 15:33:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1in2TW-0007ac-4S for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Jan 2020 15:33:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1in2TV-0007aV-Sq for pgsql-bugs@lists.postgresql.org; Thu, 02 Jan 2020 15:33:25 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1in2TO-0001Qc-Jy for pgsql-bugs@lists.postgresql.org; Thu, 02 Jan 2020 15:33:25 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 002FXFTZ017313; Thu, 2 Jan 2020 10:33:15 -0500 From: Tom Lane To: piotrwlodarczyk89@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16184: Segmentation Fault during update In-reply-to: <16184-2f718844be10c863@postgresql.org> References: <16184-2f718844be10c863@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 02 Jan 2020 15:16:45 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17311.1577979195.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 02 Jan 2020 10:33:15 -0500 Message-ID: <17312.1577979195@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > Log: > 2020-01-02 15:42:26 CET [12729]: [95-1] user=3D,db=3D,xid=3D0,state=3D00= 000 LOG: = > server process (PID 28879) was terminated by signal 11: Segmentation fau= lt > 2020-01-02 15:42:26 CET [12729]: [96-1] user=3D,db=3D,xid=3D0,state=3D00= 000 DETAIL: = > Failed process was running: UPDATE job_abstract a > SET job_status =3D 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 m= ade > 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