public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Richard Guo <[email protected]>
Cc: David Rowley <[email protected]>
Cc: Nathan Bossart <[email protected]>
Cc: Paul Ramsey <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Pg18 Recursive Crash
Date: Wed, 18 Dec 2024 19:22:40 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAMbWs48mAZZKW_pHoVZsFfHr_69G=3Vm934p227XpdxNaM0arQ@mail.gmail.com>
References: <[email protected]>
<Z2BtL7ZXEjKkHtNX@nathan>
<CAApHDvo11HBcb624eTAkXMBkN3=fji_DP+BqNYGYfNNo8nOxaQ@mail.gmail.com>
<[email protected]>
<CAMbWs4-8U9q2LAtf8+ghV11zeUReA3AmrYkxzBEv0vKnDxwkKA@mail.gmail.com>
<CAApHDvpki1oHgMKw+beUhkPMAafznUQAyVAyqyz7918RMeAt2A@mail.gmail.com>
<CAMbWs48mAZZKW_pHoVZsFfHr_69G=3Vm934p227XpdxNaM0arQ@mail.gmail.com>
Richard Guo <[email protected]> writes:
> I see. I didn't notice any real issues with that; I was just flagged
> by the XXX comment there, which raises the question of whether it's
> worth working harder to determine the inputOps.
I was intending to add some code to my nodeSetop patch to see if
both input plan nodes use the same fixed slot type, and if so
pass that rather than NULL to BuildTupleHashTableExt. Perhaps
nodeRecursiveunion could do the same thing (in which case we
probably ought to abstract that out to a subroutine).
regards, tom lane
view thread (11+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Pg18 Recursive Crash
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox