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 1fSpho-0002P6-Pr for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 20:15:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSphm-0000o7-TW for pgsql-admin@arkaria.postgresql.org; Tue, 12 Jun 2018 20:15:50 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1fSphm-0000ny-MG for pgsql-admin@lists.postgresql.org; Tue, 12 Jun 2018 20:15:50 +0000 Received: from util-st-02.imsweb.com ([204.132.58.65]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fSphd-00080t-EW for pgsql-admin@lists.postgresql.org; Tue, 12 Jun 2018 20:15:49 +0000 Received: from PAN.omni.imsweb.com (haproxy-st-02 [204.132.58.76]) by util-st-02.imsweb.com (Postfix) with ESMTP id 35317E1486; Tue, 12 Jun 2018 16:15:39 -0400 (EDT) Received: from THALASSA.omni.imsweb.com (172.22.64.102) by PAN.omni.imsweb.com (172.22.64.64) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Tue, 12 Jun 2018 16:15:39 -0400 Received: from THALASSA.omni.imsweb.com ([172.22.64.102]) by THALASSA.omni.imsweb.com ([172.22.64.102]) with mapi id 15.00.1367.000; Tue, 12 Jun 2018 16:15:38 -0400 From: "Heinemann, Manfred (IMS)" To: Tom Lane CC: "pgsql-admin@lists.postgresql.org" Subject: RE: Segmentation fault with parallelism PG 10.4 Thread-Topic: Segmentation fault with parallelism PG 10.4 Thread-Index: AdQCcNQA4J0c19/+TWKIIympNZy4gwAJdHCAAAMk7pA= Date: Tue, 12 Jun 2018 20:15:38 +0000 Message-ID: <8493b91fb47d432297fbd4d96b7cb553@THALASSA.omni.imsweb.com> References: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com> <1476.1528825515@sss.pgh.pa.us> In-Reply-To: <1476.1528825515@sss.pgh.pa.us> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [204.132.58.76] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is what I see in a stack trace Program received signal SIGSEGV, Segmentation fault. 0x000000000084dcf3 in pglz_decompress () -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us] Sent: Tuesday, June 12, 2018 1:45 PM To: Heinemann, Manfred (IMS) Cc: pgsql-admin@lists.postgresql.org Subject: Re: Segmentation fault with parallelism PG 10.4 "Heinemann, Manfred (IMS)" writes: > We allow some user querying against the database and a user wrote sql tha= t would repeatedly cause a segmentation fault. We can't share the data but = 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_b= ackend regards, tom lane ________________________________ Information in this e-mail may be confidential. It is intended only for the= addressee(s) identified above. If you are not the addressee(s), or an empl= oyee or agent of the addressee(s), please note that any dissemination, dist= ribution, or copying of this communication is strictly prohibited. If you h= ave received this e-mail in error, please notify the sender of the error.