From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' |
Date: | 2024-12-10 02:12:32 |
Message-ID: | 4167039.1733796752@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> FWIW, I have a hard time understanding why ignoring "LMT", which is
> a timezone abbreviation meaning "Local Mean Time", in datetktbl[],
> which is a table for date/time keywords, is the right thing to do.
I agree. We should be mapping it to whatever GMT offset "LMT" means
in the selected zone (assuming there is an entry, which it seems like
there is in most of them). I've not gotten around to looking at what
that would take, but it's probably not entirely trivial, since it
would mean different GMT offsets in different zones.
One thing that might be interesting to look at is whether the same
mechanism could be used for other TZ abbreviations defined by the tzdb
data, instead of relying on our hard-wired lists.
> Worth noting that we may want to do something in ECPG's dt_common.c as
> well, that holds a similar table with TZ abbreviation data and LMT is
> missing there?
ECPG's datetime support is so far behind the server's that it's kind
of sad. But bringing it up to speed would be a large investment of
effort, something I for one am not prepared to put into it. I sure
don't think we should hold up fixing this on the server side pending
making that happen.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vladislav Malyshkin | 2024-12-10 13:18:53 | postgres 16 index double variable seems to fail. postgres 15 OK |
Previous Message | Michael Paquier | 2024-12-10 00:26:02 | Re: TimestampTz->Text->TimestampTz casting fails with DateStyle 'Postgres' |