Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Дата
Msg-id 5667.1502144841@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values  (Peter Geoghegan <pg@bowt.ie>)
Список pgsql-bugs
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> It has never been the case that there is a guarantee that a new
> operating system environment will have the same or more collations
> available as an earlier version.  Even glibc removes or renames locales.

Indeed, and one of the alleged selling points of ICU was greater stability
of collation behaviors (including naming).  I'd like to try to actually
achieve that.

> In this particular case, you can create user-defined collations to fill
> in the missing names if you want.

NO. YOU. CAN'T.  At least not with convenient upgrade methods like
pg_upgrade.  If the collation name isn't produced by the newer version's
initdb, pg_upgrade will fail.
        regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: [BUGS] Crash report for some ICU-52 (debian8) COLLATE andwork_mem values