Re: Should AT TIME ZONE be volatile?

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

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-11T18:38:13Z

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 →

Revert per-index collation version tracking feature.
- ec4831470826 14.0 cited

Robert Haas <robertmhaas@gmail.com> writes:
> I agree with Tom that it sounds like a lot of work. And to be honest
> it's work that I don't really feel very excited about.

Even if you were excited about it, would maintaining such data be
a good use of project resources?  It's not like we lack other things
we ought to be doing.  I agree that the lack of reliable versioning
info is a problem, but I can't see that "let's fork ICU and tzdb too"
is a good answer.

			regards, tom lane