| From: | Aleksander Alekseev <aleksander(at)timescale(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, 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:14:06 |
| Message-ID: | CAJ7c6TNPUy4_HVYFHMu0AU7_UpR-bHJmh94E+DPKT2fxT-OgQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> > 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.
It was worth a try :) Good to know then, I will move the CF entry to
the next commitfest. Thanks!
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2025-04-10 12:19:37 | Re: PostgreSQL 18 Release Management Team & Feature Freeze |
| Previous Message | Heikki Linnakangas | 2025-04-10 12:11:00 | Re: PostgreSQL 18 Release Management Team & Feature Freeze |