| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Subject: | Re: PostgreSQL 18 Release Management Team & Feature Freeze |
| Date: | 2025-04-10 12:11:00 |
| Message-ID: | 1af72b53-432c-4523-a8c3-277dbd46b541@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/04/2025 14:57, Aleksander Alekseev wrote:
> Let me be the first author this year who asks to squeeze his patch in
> after feature freeze :D
:-)
> Do you think that it's worth merging SLRU refactoring into PG18, or is
> it considered a feature? [1] This is arguably not the top priority and
> we could wait for another year but merging it now doesn't seem to be
> too much of a burden either.
>
> [1]: https://commitfest.postgresql.org/patch/5250/
I would consider that a feature, too late for v18. There's not
particular benefit in getting it into v18 vs later.
--
Heikki Linnakangas
Neon (https://neon.tech)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2025-04-10 12:14:06 | Re: PostgreSQL 18 Release Management Team & Feature Freeze |
| Previous Message | Aleksander Alekseev | 2025-04-10 11:57:28 | Re: PostgreSQL 18 Release Management Team & Feature Freeze |