Re: unrecognized node type while displaying a Path due to dangling pointer - Mailing list pgsql-hackers

From Tom Lane
Subject Re: unrecognized node type while displaying a Path due to dangling pointer
Date
Msg-id 2602263.1689128614@sss.pgh.pa.us
Whole thread Raw
In response to Re: unrecognized node type while displaying a Path due to dangling pointer  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: unrecognized node type while displaying a Path due to dangling pointer
List pgsql-hackers
David Rowley <dgrowleyml@gmail.com> writes:
> I've not taken the time to fully understand this, but from reading the
> thread, I'm not immediately understanding why we can't just shallow
> copy the Path from the other RelOptInfo and replace the parent before
> using it in the upper RelOptInfo.  Can you explain?

I did think about that, but "shallow copy a Path" seems nontrivial
because the Path structs are all different sizes.  Maybe it is worth
building some infrastructure to support that?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: DROP DATABASE is interruptible
Next
From: Andres Freund
Date:
Subject: Re: Forgive trailing semicolons inside of config files