Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSnMH-0006xM-OX for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 17:45:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSnMG-0007Ef-4p for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 17:45:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSnMF-0007EI-Q0 for pgsql-admin@lists.postgresql.org; Tue, 12 Jun 2018 17:45:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSnM9-0007SO-7w for pgsql-admin@lists.postgresql.org; Tue, 12 Jun 2018 17:45:26 +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 w5CHjF3c001477; Tue, 12 Jun 2018 13:45:15 -0400 From: Tom Lane To: "Heinemann, Manfred (IMS)" cc: "pgsql-admin@lists.postgresql.org" Subject: Re: Segmentation fault with parallelism PG 10.4 In-reply-to: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com> References: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com> Comments: In-reply-to "Heinemann, Manfred (IMS)" message dated "Tue, 12 Jun 2018 17:36:16 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1475.1528825515.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 12 Jun 2018 13:45:15 -0400 Message-ID: <1476.1528825515@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "Heinemann, Manfred (IMS)" writes: > We allow some user querying against the database and a user wrote sql th= at would repeatedly cause a segmentation fault. We can't share the data bu= t I will show what I can. The info you've provided is not of much help, but if you could show a stack trace from the point of the segfault, that might narrow things down. https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_= backend regards, tom lane