From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@lists.postgresql.org, Hadi Moshayedi <hadi@moshayedi.net>
Subject: Re: tableam scan-API patch broke foreign key validation
Date: Thu, 25 Apr 2019 14:20:52 -0400
Message-ID: <20190425182052.GA391@alvherre.pgsql> (raw)
In-Reply-To: <13344.1554578481@sss.pgh.pa.us>
On 2019-Apr-06, Tom Lane wrote:
> BTW, I just stumbled across a different bug in v11 by trying to run
> HEAD's test script on it ... not sure if that's a known problem or not:
>
> (gdb) f 3
> #3 0x000000000063949c in ExecSetupPartitionTupleRouting (
> mtstate=<value optimized out>, rel=0x7f343e4f4170) at execPartition.c:201
> 201 Assert(update_rri_index == num_update_rri);
> (gdb) bt
> #0 0x00000037b6232495 in raise (sig=6)
> at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
For closure: this was re-reported as
https://www.postgresql.org/message-id/20710.1554582479@sss.pgh.pa.us
and the fix committed as 10e3991fad8a300ed268878ae30c96074628c1e1.
Thanks
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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-hackers@postgresql.org
Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, andres@anarazel.de, hadi@moshayedi.net
Subject: Re: tableam scan-API patch broke foreign key validation
In-Reply-To: <20190425182052.GA391@alvherre.pgsql>
* 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