From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
---|---|
To: | Tender Wang <tndrwang(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Amit Langote <amitlangote09(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, m_lingbin(at)126(dot)com, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Subject: | Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally |
Date: | 2025-02-12 13:55:43 |
Message-ID: | CAMbWs4_BF-WB858BLn5yG72RQdibdi7=yGHYMRTGxJe5cDmW7w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Feb 12, 2025 at 7:48 PM Tender Wang <tndrwang(at)gmail(dot)com> wrote:
> Tender Wang <tndrwang(at)gmail(dot)com> 于2025年2月12日周三 17:48写道:
> When we create join rel for (2,5), then wen enter try_partitionwise_join().
> In this func, we call build_child_join_sjinfo() to build SpecialJoinInfo for child.
> In build_child_join_sjinfo(), we use memcpy(), I think we should use copyObject().
> Otherwise, the parent_sjinfo will be freed, for example, after call free_child_join_sjinfo(),
> the parent_sjinfo min_lefthand looks like as below:
>
> (gdb) p *parent_sjinfo->min_lefthand
> $7 = {type = 3951489872, nwords = 21994, words = 0x55eaeb8696b0}
>
> The above bitmap is invalid, so trigger the Assert(bms_is_valid_set(a));
Nice catch! We should avoid freeing the members of child_sjinfo
unless they are translated copies of their counterparts in
parent_sjinfo.
Thanks
Richard
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2025-02-12 14:04:07 | Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally |
Previous Message | PG Bug reporting form | 2025-02-12 12:53:21 | BUG #18807: libcrypto.so.1.1: cannot open shared object file |