Re: CF entries for 17 to be reviewed

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
Subject: Re: CF entries for 17 to be reviewed
Date: 2024-03-15 14:28:32
Message-ID: CAJ7c6TObUGFJwE7Db9b+KkcTCjqSZfVMRj4MAtW27TGA08_k7Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> > 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:
>
> [...]
>
> * (to be continued)

Server Features:

* Custom storage managers (SMGR), redux
The patch needs a rebase. I notified the authors.
* pg_tracing
Ditto. The patch IMO is promising. I encourage anyone interested in
the topic to take a look.
* Support run-time partition pruning for hash join
The patch needs (more) review. It doesn't look extremely complex.
* Support prepared statement invalidation when result or argument types change
I changed the status to "Waiting on Author". The patch needs a
rebase since January.
* Allow INSTEAD OF DELETE triggers to modify the tuple for RETURNING
Needs rebase.

--
Best regards,
Aleksander Alekseev

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bertrand Drouvot 2024-03-15 14:44:43 Re: Synchronizing slots from primary to standby
Previous Message Nathan Bossart 2024-03-15 14:28:31 Re: Introduce XID age and inactive timeout based replication slot invalidation