Re: IANA timezone abbreviations versus timezone_abbreviations

From: Aleksander Alekseev <aleksander(at)timescale(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: IANA timezone abbreviations versus timezone_abbreviations
Date: 2025-01-08 09:50:17
Message-ID: CAJ7c6TNVgWdrTrVK_bfK9BN7NTtF6wFu1PZG9GGRFySq1t5AeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Tom,

> This mess was brought up in pgsql-bugs [1], but the solution
> I propose here is invasive enough that I think it needs
> discussion on -hackers.
>
> [...]

I tested and reviewed the patch. It fixes the originally reported bug
and looks good to me.

> The only other way I can envision to remove the round-trip hazard
> is to stop using alphabetic abbreviations at all in timestamp
> output, and use numeric GMT offsets regardless of datestyle.
> I doubt that would make many people happy. It would certainly
> break a bunch of our own regression tests, and I expect it would
> break other people's applications too.

I think we need to introduce alternative data types e.g. datetime /
datetimetz pair if we want to do this.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-01-08 09:52:48 Re: Conflict detection for update_deleted in logical replication
Previous Message Alvaro Herrera 2025-01-08 09:47:48 Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints