From: Heinemann, Manfred (IMS) <HeinemannM@imsweb.com>
To: 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
Date: Mon, 2 Jul 2018 18:27:43 +0000
Message-ID: <0825ba4b6ed848cb9154b4e8794e6ada@THALASSA.omni.imsweb.com> (raw)
In-Reply-To: <21009.1529421245@sss.pgh.pa.us>
References: <8577044f0d2f4fe3919c53c2f7a642e5@THALASSA.omni.imsweb.com>
<1476.1528825515@sss.pgh.pa.us>
<8493b91fb47d432297fbd4d96b7cb553@THALASSA.omni.imsweb.com>
<44f8d9c203124535b497f2a79ceac59d@THALASSA.omni.imsweb.com>
<21009.1529421245@sss.pgh.pa.us>
Here is what I get for the stack trace, is it more helpful?
Program received signal SIGSEGV, Segmentation fault.
0x000000000084dcb0 in pglz_decompress ()
#0 0x000000000084dcb0 in pglz_decompress ()
#1 0x00000000004b8d2f in toast_decompress_datum ()
#2 0x0000000000793ce0 in numeric_eq ()
#3 0x00000000005e68eb in ExecInterpExpr ()
#4 0x00000000005ef589 in ExecScan ()
#5 0x0000000000608784 in ExecNestLoop ()
#6 0x00000000005fc6b5 in ExecGather ()
#7 0x00000000005feb35 in ExecHashJoin ()
#8 0x00000000006086d4 in ExecNestLoop ()
#9 0x00000000005e9b02 in standard_ExecutorRun ()
#10 0x000000000071305b in PortalRunSelect ()
#11 0x00000000007142d1 in PortalRun ()
#12 0x000000000071038b in exec_simple_query ()
#13 0x0000000000711589 in PostgresMain ()
#14 0x0000000000476399 in ServerLoop ()
#15 0x00000000006a9acc in PostmasterMain ()
#16 0x000000000062b58c in main ()
Thanks,
Manfred
>"Heinemann, Manfred (IMS)" <HeinemannM@imsweb.com> writes:
>> Is this stack trace helpful at all?
>
>No, because it isn't actually a stack trace, just the top frame. See
>
>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 employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.
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: HeinemannM@imsweb.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
Subject: RE: Segmentation fault with parallelism PG 10.4
In-Reply-To: <0825ba4b6ed848cb9154b4e8794e6ada@THALASSA.omni.imsweb.com>
* 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