Re: Should AT TIME ZONE be volatile?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Shay Rojansky <roji(at)roji(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Should AT TIME ZONE be volatile?
Date: 2021-11-11 14:52:52
Message-ID: 1546724.1636642372@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I'm not really convinced that ICU is better, either. I think it's more
> that it isn't used as much.

Well, at least ICU has a notion of attaching versions to collations.
How mindful they are of bumping the version number when necessary
remains to be seen. But the POSIX locale APIs don't even offer the
opportunity to get it right.

> I don't have any constructive proposal for what to do about any of
> this. It sure is frustrating, though.

Yup. If we had reliable ways to detect changes in this sort of
environment-supplied data, maybe we could do something about it
(a la the work that's been happening on attaching collation versions
to indexes). But personally I can't summon the motivation to work
on that, when ICU is the *only* such infrastructure that offers
readily program-readable versioning.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-11-11 15:11:49 Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display
Previous Message Robert Haas 2021-11-11 14:21:59 Re: Should AT TIME ZONE be volatile?