From: "Heinemann, Manfred (IMS)" <HeinemannM@imsweb.com>
To: "Heinemann, Manfred (IMS)" <HeinemannM@imsweb.com>, Tom Lane
	<tgl@sss.pgh.pa.us>
CC: "pgsql-admin@lists.postgresql.org" <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/+TWKIIympNZy4gwAJdHCAAAMk7pABTkewkA==
Date: Tue, 19 Jun 2018 14:49:53 +0000
Message-ID: <44f8d9c203124535b497f2a79ceac59d@THALASSA.omni.imsweb.com>
References: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com>
 <1476.1528825515@sss.pgh.pa.us>
 <8493b91fb47d432297fbd4d96b7cb553@THALASSA.omni.imsweb.com>
In-Reply-To: <8493b91fb47d432297fbd4d96b7cb553@THALASSA.omni.imsweb.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: bulk

Is this stack trace helpful at all?
Is there anything else I could do to investigate?

Thanks,
Manfred

>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) <HeinemannM@imsweb.com>
>>Cc: pgsql-admin@lists.postgresql.org
>>Subject: Re: Segmentation fault with parallelism PG 10.4
>>
>>"Heinemann, Manfred (IMS)" <HeinemannM@imsweb.com> writes:
>>> We allow some user querying against the database and a user wrote sql t=
hat 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 sta=
ck 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
________________________________

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.


________________________________

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.