From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: PostgreSQL 17 Release Management Team & Feature Freeze |
Date: | 2024-04-04 02:10:27 |
Message-ID: | CAApHDvoCZpsB3L=QPKDCpPR9W2rN=XaPngCoHxOkNn-Byp1+cQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 18 Mar 2024 at 15:50, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Additionally, the RMT has set the feature freeze to be **April 8, 2024
> at 0:00 AoE** (see [1]). This is the last time to commit features for
> PostgreSQL 17. In other words, no new PostgreSQL 17 feature can be
> committed after April 8, 2024 at 0:00 AoE. As mentioned last year in
> [2], this uses the "standard" feature freeze date/time.
Someone asked me about this, so thought it might be useful to post here.
To express this as UTC, It's:
postgres=# select '2024-04-08 00:00-12:00' at time zone 'UTC';
timezone
---------------------
2024-04-08 12:00:00
Or, time remaining, relative to now:
select '2024-04-08 00:00-12:00' - now();
David
> [1]: https://en.wikipedia.org/wiki/Anywhere_on_Earth
> [2]: https://www.postgresql.org/message-id/9fbe60ec-fd1b-6ee0-240d-af7fc444223d@postgresql.org
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-04-04 02:35:58 | Re: Using the %m printf format more |
Previous Message | Michael Paquier | 2024-04-04 01:58:48 | Re: Refactoring of pg_resetwal/t/001_basic.pl |