Horton

Re: Should AT TIME ZONE be volatile?

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Shay Rojansky <roji@roji.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2021-11-11T19:23:34Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Revert per-index collation version tracking feature.

Robert Haas <robertmhaas@gmail.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