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