From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heinemann, Manfred (IMS) <HeinemannM@imsweb.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: Segmentation fault with parallelism PG 10.4
Date: Tue, 12 Jun 2018 13:45:15 -0400
Message-ID: <1476.1528825515@sss.pgh.pa.us> (raw)
In-Reply-To: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com>
References: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com>
"Heinemann, Manfred (IMS)" <HeinemannM@imsweb.com> writes:
> We allow some user querying against the database and a user wrote sql that 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_backend
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, HeinemannM@imsweb.com, pgsql-admin@lists.postgresql.org
Subject: Re: Segmentation fault with parallelism PG 10.4
In-Reply-To: <1476.1528825515@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