| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: RFC: extensible planner state |
| Date: | 2025-09-24 16:49:14 |
| Message-ID: | 3442057.1758732554@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> Cool... except I thought that the release freeze wouldn't lift until
> we release, which I thought was tomorrow?
Nope, the freeze is over as soon as the git tag for the release is
pushed, cf
https://wiki.postgresql.org/wiki/Committing_checklist#Release_freezes
We'd unfreeze when the stamping commit is made, except that we want
some breathing room for a re-wrap if a packager discovers a critical
problem. We give them 24 hours to report that.
(What happens if a critical problem is discovered shortly later?
We'd probably use a new minor release number in that case.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-09-24 16:52:09 | Re: Clarification on Role Access Rights to Table Indexes |
| Previous Message | Fujii Masao | 2025-09-24 16:40:27 | Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ? |