* Tom Lane (tgl@sss.pgh.pa.us) wrote:
> On looking closer, though, it's *still* messy and unobvious :-(.
> There is no single place in the parser where we have the complete
> multi-level query tree available in a convenient form for this sort of
> postprocessing.
That's unfortunate. :/
> I've thought of a less painful variant of my third option: instead of
> making a permanent addition to RangeTblEntry, we can have a transient
> data structure attached to ParseState that lets us find the JoinExpr
> nodes for already-parsed joins. I'm going to try that next.
Sounds reasonable. I'd be happy to help if there's anything useful I
can do at this point.
Thanks,
Stephen