Re: automating RangeTblEntry node support

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: automating RangeTblEntry node support
Date: 2024-03-22 06:49:51
Message-ID: f61c3e3f-2b04-4eb1-b343-9f71a7a233b0@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey M. Borodin 2024-03-22 06:53:51 Re: UUID v7
Previous Message Tom Lane 2024-03-22 06:15:27 Re: Regression tests fail with musl libc because libpq.so can't be loaded