Re: RFC: extensible planner state - Mailing list pgsql-hackers

From Tom Lane
Subject Re: RFC: extensible planner state
Date
Msg-id 3442057.1758732554@sss.pgh.pa.us
Whole thread Raw
In response to Re: RFC: extensible planner state  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.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



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: vacuumdb --analyze-only does not need to issue VACUUM (ONLY_DATABASE_STATS) ?
Next
From: Nathan Bossart
Date:
Subject: Re: Clarification on Role Access Rights to Table Indexes