Horton

Re: automating RangeTblEntry node support

Peter Eisentraut <peter@eisentraut.org>

View thread View on postgr.es
From: Peter Eisentraut <peter@eisentraut.org>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Matthias van de Meent <boekewurm+postgres@gmail.com>, Paul Jungwirth <pj@illuminatedcomputing.com>, pgsql-hackers@lists.postgresql.org
Date: 2024-03-22T06:49:51Z
Lists: pgsql-hackers 
On 21.03.24 10:51, Andrew Dunstan wrote:
>     At this point, I'm not too stressed about pressing forward with these
>     last two patches.  We can look at them again perhaps if we make
>     progress
>     on a more compact node output format.  When I started this thread, I
>     had
>     a lot of questions about various details about the RangeTblEntry
>     struct,
>     and we have achieved many answers during the discussions, so I'm happy
>     with the progress.  So for PG17, I'd like to just do patches 0001..0005.
> 
> Patches 1 thru 5 look good to me

Thanks for checking.  I have committed these (1 through 5) and will 
close the commit fest entry.

Commits

  1. Make RangeTblEntry dump order consistent

  2. Remove custom _jumbleRangeTblEntry()

  3. Reformat some node comments

  4. Improve comment

  5. Remove obsolete comment

  6. Remove custom Constraint node read/write implementations