Re: Pg18 Recursive Crash

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Paul Ramsey <pramsey(at)cleverelephant(dot)ca>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pg18 Recursive Crash
Date: 2024-12-19 00:11:39
Message-ID: CAMbWs48mAZZKW_pHoVZsFfHr_69G=3Vm934p227XpdxNaM0arQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 18, 2024 at 7:45 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> On Wed, 18 Dec 2024 at 22:29, Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> > Should we be concerned about passing a NULL TupleTableSlotOps in
> > nodeRecursiveUnion.c?
>
> I made it pass NULL on purpose because the slot type on the recursive
> union can be different on the inner and outer sides. Do you see issues
> with that?

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.

Thanks
Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-12-19 00:13:27 Re: Pg18 Recursive Crash
Previous Message Anton A. Melnikov 2024-12-19 00:10:30 Re: Change GUC hashtable to use simplehash?