Re: Should AT TIME ZONE be volatile? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Should AT TIME ZONE be volatile?
Date
Msg-id CA+TgmoZCcVyz2kdhjm305iR15jafV5Ron-kLMO0gkYg6b4YQQA@mail.gmail.com
Whole thread Raw
In response to Re: Should AT TIME ZONE be volatile?  (Isaac Morland <isaac.morland@gmail.com>)
Responses Re: Should AT TIME ZONE be volatile?
List pgsql-hackers
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
coveredby the collation I would have expected to cause an error at insert time. But definitely I agree I wouldn't feel
confidentabout 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



pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: archive modules
Next
From: Tom Lane
Date:
Subject: Re: simplifying foreign key/RI checks