| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, rmt(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Feature freeze timezone change request |
| Date: | 2026-03-19 00:40:55 |
| Message-ID: | 1087265.1773880855@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:
> On Wed, Mar 18, 2026 at 7:07 PM Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
>> I was notified that the tentative feature freeze timestamp is on the
>> wiki[1] as: April 8, 2026 0:00 UTC-12
>> I request that the final feature freeze timestamp be set to 0:00 UTC,
>> not 0:00 UTC-12.
> +1.
I think the UTC-12 business is left over from when we defined it as
AoE, but we're not doing that anymore because it's too confusing.
What we've been using lately for release freezes is noon UTC, which
personally I'd prefer on the grounds that it's not as confusing
which day is meant.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lukas Fittl | 2026-03-19 00:45:49 | Re: Stack-based tracking of per-node WAL/buffer usage |
| Previous Message | Chao Li | 2026-03-19 00:08:26 | Re: dshash_find_or_insert vs. OOM |