| 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>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Subject: | Re: PostgreSQL 18 Release Management Team & Feature Freeze |
| Date: | 2025-04-10 12:19:37 |
| Message-ID: | 8242d1cc-ee5b-488e-aeac-6b13f5cb83d6@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
On that note, I spoke with Matthias off-list, and he pointed out this patch:
It makes changes to the table AM API, to fix an existing bug. If that's
how we want to fix it, now's the last chance to make table AM API
changes for v18.
An argument against doing it now is that we need to come up with a
back-patchable fix anyway. That'll probably be more hacky, but there's
little harm in doing it the the same hacky way for one more release.
(I have not looked at the patches, so don't know if there are other issues)
--
Heikki Linnakangas
Neon (https://neon.tech)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tefft, Michael J | 2025-04-10 12:22:16 | Capturing both IP address and hostname in the log |
| Previous Message | Aleksander Alekseev | 2025-04-10 12:14:06 | Re: PostgreSQL 18 Release Management Team & Feature Freeze |