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: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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 19:23:34
Message-ID: 1580689.1636658614@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:
> ... but we want
> collation definitions that *actually don't change*.

Um ... how would that work? Unicode is a moving target. Even without
their continual addition of stuff, I'm not convinced that social rules
about how to sort are engraved on stone tablets. The need for collation
updates may not be as predictable as the need for timezone updates,
but I doubt that we can just freeze the data forever.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-11-11 19:41:47 Re: Should AT TIME ZONE be volatile?
Previous Message Tom Lane 2021-11-11 19:17:59 Re: Should AT TIME ZONE be volatile?