Re: Should AT TIME ZONE be volatile?
От | Robert Haas |
---|---|
Тема | Re: Should AT TIME ZONE be volatile? |
Дата | |
Msg-id | CA+TgmoYDZo5oqz1SnXbBn48S4je0SU+E2F4tJ9EJyVk9=e7sUA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Should AT TIME ZONE be volatile? (Isaac Morland <isaac.morland@gmail.com>) |
Ответы |
Re: Should AT TIME ZONE be volatile?
|
Список | pgsql-hackers |
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 existingcharacters. 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. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: