Re: Should AT TIME ZONE be volatile?

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Isaac Morland <isaac.morland@gmail.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Laurenz Albe <laurenz.albe@cybertec.at>, Shay Rojansky <roji@roji.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2021-11-11T23:08:47Z

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

On Thu, Nov 11, 2021 at 5:04 PM Isaac Morland <isaac.morland@gmail.com> wrote:
> Wouldn't an existing index only have characters that were already part of the collation? Attempting to use one not covered by the collation I would have expected to cause an error at insert time. But definitely I agree I wouldn't feel confident about the safety of any change.

I mean it's not like we are updating the definition of
pg_utf8_verifychar() every time they define a new code point.

-- 
Robert Haas
EDB: http://www.enterprisedb.com