| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, 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 16:08:18 |
| Message-ID: | 9373201a-27de-4026-8da1-392196144a55@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/19/26 11:37, Jacob Champion wrote:
> 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.
+1 seems reasonable and not likely to be misunderstood
--
Joe Conway
PostgreSQL Contributors Team
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2026-03-19 16:19:53 | Re: Eliminating SPI / SQL from some RI triggers - take 3 |
| Previous Message | Joe Conway | 2026-03-19 16:06:13 | Re: Emitting JSON to file using COPY TO |