From: | Kohei KaiGai <kaigai(at)heterodb(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Asymmetric partition-wise JOIN |
Date: | 2019-12-27 07:34:30 |
Message-ID: | CAOP8fzaDAP_6dR0VbCQrc5smcdzvwx5vEafs6bNhEesP0VP2KA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
This crash was reproduced on our environment also.
It looks to me adjust_child_relids_multilevel() didn't expect a case
when supplied 'relids'
(partially) indicate normal and non-partitioned relation.
It tries to build a new 'parent_relids' that is a set of
appinfo->parent_relid related to the
supplied 'child_relids'. However, bits in child_relids that indicate
normal relations are
unintentionally dropped here. Then, adjust_child_relids_multilevel()
goes to an infinite
recursion until stack limitation.
The attached v2 fixed the problem, and regression test finished correctly.
Best regards,
2019年12月1日(日) 12:24 Michael Paquier <michael(at)paquier(dot)xyz>:
>
> On Sat, Aug 24, 2019 at 05:33:01PM +0900, Kohei KaiGai wrote:
> > On the other hands, it eventually consumes almost equivalent amount
> > of memory to load the inner relations, if no leafs are pruned, and if we
> > could extend the Hash-node to share the hash-table with sibling
> > join-nodess.
>
> The patch crashes when running the regression tests, per the report of
> the automatic patch tester. Could you look at that? I have moved the
> patch to nexf CF, waiting on author.
> --
> Michael
--
HeteroDB, Inc / The PG-Strom Project
KaiGai Kohei <kaigai(at)heterodb(dot)com>
Attachment | Content-Type | Size |
---|---|---|
gdb_back_trace.txt | text/plain | 7.1 KB |
pgsql13-asymmetric-partitionwise-join.v2.patch | application/octet-stream | 21.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2019-12-27 08:20:15 | Re: Reorderbuffer crash during recovery |
Previous Message | Julien Rouhaud | 2019-12-27 06:29:48 | Re: Duplicate Workers entries in some EXPLAIN plans |