On Thu, Apr 10, 2025 at 03:11:00PM +0300, Heikki Linnakangas wrote:
> On 10/04/2025 14:57, Aleksander Alekseev wrote:
>> 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
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.postgr
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
On that note, I spoke with Matthias off-list, and he pointed out this patch:
https://www.postgresql.org/message-id/CAEze2Wh9JjLKdN3dHPF%3DNejzf%3D9fDfcY
Hi,
> We are pleased to announce the Release Management Team (RMT) (cc'd) for
> the PostgreSQL 18 release:
>
> - Tomas Vondra
> - Nathan Bossart
> - Heikki Linnakangas
>
> You can find information about the responsibilities of the RMT here:
> https://wiki.postgresql.org/wiki/Release_Management_Tea
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 co
Hi,
We are pleased to announce the Release Management Team (RMT) (cc'd) for
the PostgreSQL 18 release:
- Tomas Vondra
- Nathan Bossart
- Heikki Linnakangas
You can find information about the responsibilities of the RMT here:
https://wiki.postgresql.org/wiki/Release_Management_Team
We have no
