Hi,
> > On 6 Mar 2024, at 18:49, Andrey M. Borodin <x4mmm@yandex-team.ru> wrote:
> >
> > Here are statuses for "Refactoring" section:
>
> [...]
> Aleksander, I would greatly appreciate if you join me in managing CF. Together we can move more stuff :)
> Currently, I'm going through "SQL Commands". And so far I had not come to "Performance" and "Server Features" at
all...So if you can handle updating statuses of that sections - that would be great.
Server Features:
* Fix partitionwise join with partially-redundant join clauses
I see there is a good discussion in the progress here. Doesn't
seem to be needing more reviewers at the moment.
* ALTER TABLE SET ACCESS METHOD on partitioned tables
Ditto.
* Patch to implement missing join selectivity estimation for range types
The patch doesn't apply and has been "Waiting on Author" for a few
months now. Could be a candidate for closing with RwF.
* logical decoding and replication of sequences, take 2
According to Tomas Vondra the patch is not ready for PG17. The
patch is marked as "Waiting on Author". Although it could be withrowed
for now, personally I see no problem with keeping it WoA until the
PG18 cycle begins.
* Add the ability to limit the amount of memory that can be allocated
to backends
v20231226 doesn't apply. The patch needs love from somebody interested in it.
* Multi-version ICU
By a quick look the patch doesn't apply and was moved between
several commitfests, last time in "Waiting on Author" state. Could be
a candidate for closing with RwF.
* Post-special Page Storage TDE support
A large patch divided into 28 (!) parts. Currently needs a rebase.
Which shouldn't necessarily stop a reviewer looking for a challenging
task.
* Built-in collation provider for "C" and "C.UTF-8"
Peter E left some feedback today, so I changed the status to
"Waiting on Author"
* ltree hash functions
Marked as RfC and cfbot seems to be happy with the patch. Could
use some attention from a committer?
* UUID v7
The patch is in good shape. Michael argued that the patch should
be merged when RFC is approved. No action seems to be needed until
then.
* (to be continued)
--
Best regards,
Aleksander Alekseev
