Re: Collation versioning
От | Robert Haas |
---|---|
Тема | Re: Collation versioning |
Дата | |
Msg-id | CA+TgmoZSCjinh6Sfoofp2tfweFvQxXoCUNv+dyJnS6PzNGv_LA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Collation versioning (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: Collation versioning
|
Список | pgsql-hackers |
On Tue, Nov 26, 2019 at 3:44 PM Thomas Munro <thomas.munro@gmail.com> wrote: > I suppose another reason to use such a switch would be if there is a > change in the versioning scheme; for example, as of today in master we > are using the glibc version, but a future glibc release might offer an > interface to query the CLDR version it's using, and then a future > release of PostgreSQL might get support for that, so the strings would > change between major version of PostgreSQL but you might want to be > able to tell pg_upgrade that your indexes are good. Yeah, I like #3 too. If we're going to the trouble to build all of this mechanism, it seems worth it to build the additional machinery to be precise about the difference between "looks like a problem" and "we don't know". -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: