Horton

Re: Should AT TIME ZONE be volatile?

Isaac Morland <isaac.morland@gmail.com>

View thread
From: Isaac Morland <isaac.morland@gmail.com>
To: Robert Haas <robertmhaas@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-11T22:04:39Z
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.

On Thu, 11 Nov 2021 at 16:08, Robert Haas <robertmhaas@gmail.com> wrote:

> On Thu, Nov 11, 2021 at 3:45 PM Isaac Morland <isaac.morland@gmail.com>
> wrote:
> > There is however one kind of change at least that I think can be made
> safely: adding a new character in between existing characters. That
> shouldn't affect any existing indexes.
>
> Only if you can guarantee that said character is not present already.
> I don't think we update the end of the acceptable code point range
> every time that Unicode adds new stuff, so probably those things are
> subject to some default rule unless and until someone installs
> something more specific.  Therefore I doubt that even this case is
> truly safe.
>

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.