| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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 15:37:11 |
| Message-ID: | CAOYmi+mQMvUJpyfmmH6O3s7FJjPYgD0KpPwDez1k-HBBFZyZiQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 18, 2026 at 5:41 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Yeah -- I swapped it recently because I noticed it was still labeled
AoE, and I didn't want anyone to have to rediscover last year's
thread. It wasn't really meant to be an endorsement for UTC-12.
> 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.
+1 for 12:00 UTC.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-03-19 15:47:29 | Re: Avoiding memory leakage in jsonpath evaluation |
| Previous Message | Fujii Masao | 2026-03-19 15:29:46 | Re: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY) |