From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel WM <dwilches@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org, Andres Freund <andres@anarazel.de>
Subject: Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
Date: Sat, 14 Mar 2020 17:21:04 -0400
Message-ID: <21088.1584220864@sss.pgh.pa.us> (raw)
In-Reply-To: <CAEbtaO39qxx7GX=u8j02y5K2eyVGT8gyCOLHS2KNENQS=w_D7Q@mail.gmail.com>
References: <16293-26f5777d10143a66@postgresql.org>
<28203.1583878791@sss.pgh.pa.us>
<CAEbtaO3wTbx-DOh+B9UfNpoS2N4nQm25Y1DLrNNN_U1-8qNnqg@mail.gmail.com>
<CAEbtaO39qxx7GX=u8j02y5K2eyVGT8gyCOLHS2KNENQS=w_D7Q@mail.gmail.com>
Daniel WM <dwilches@gmail.com> writes:
> I have finally isolated the issue and I have a set of steps that reliably
> cause the segfault:
Interesting. I do *not* see a crash in v12 or HEAD, but v11 gives
me an assertion failure:
TRAP: FailedAssertion("!(!slot->tts_fixedTupleDescriptor)", File: "execTuples.c", Line: 284)
2020-03-14 17:16:06.626 EDT [1101] LOG: server process (PID 20822) was terminated by signal 6: Aborted
2020-03-14 17:16:06.626 EDT [1101] DETAIL: Failed process was running: INSERT INTO parent_table VALUES ('2020-02-02 01:00:00+00:00', 'f');
here:
#3 0x000000000063ef45 in ExecSetSlotDescriptor (slot=0x1cf4060,
tupdesc=0x7f903a2dd0f8) at execTuples.c:284
#4 0x00000000006360eb in ExecConstraints (resultRelInfo=0x1cf47b8,
slot=0x1cf4060, estate=0x1cf3778) at execMain.c:2062
#5 0x000000000065a44d in ExecInsert (mtstate=0x1cf3ae0, slot=0x1cf4060,
planSlot=0x1cf4060, estate=0x1cf3778, canSetTag=true)
at nodeModifyTable.c:398
#6 0x000000000065b80b in ExecModifyTable (pstate=<value optimized out>)
at nodeModifyTable.c:2159
#7 0x0000000000636c27 in ExecProcNode (queryDesc=0x1ce51e8,
direction=<value optimized out>, count=0, execute_once=224)
at ../../../src/include/executor/executor.h:247
#8 ExecutePlan (queryDesc=0x1ce51e8, direction=<value optimized out>,
count=0, execute_once=224) at execMain.c:1723
#9 standard_ExecutorRun (queryDesc=0x1ce51e8,
direction=<value optimized out>, count=0, execute_once=224)
So this looks like something to do with Andres' tupletableslot work.
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, dwilches@gmail.com, andres@anarazel.de
Subject: Re: BUG #16293: postgres segfaults and returns SQLSTATE 08006
In-Reply-To: <21088.1584220864@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