Re: ICU for global collation

Поиск
Список
Период
Сортировка
От Marina Polyakova
Тема Re: ICU for global collation
Дата
Msg-id 7ad26354e75259f59c4a6c6997b8ee32@postgrespro.ru
обсуждение исходный текст
Ответ на Re: ICU for global collation  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Ответы Re: ICU for global collation  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
My colleague Andrew Bille found another bug in master 
(b4e936859dc441102eb0b6fb7a104f3948c90490) and REL_15_STABLE 
(2c63b0930aee1bb5c265fad4a65c9d0b62b1f9da): pg_collation.colliculocale 
is not dumped. See check_icu_locale.sh:

In the old cluster:
SELECT collname, colliculocale FROM pg_collation WHERE collname = 
'testcoll_backwards'
       collname      |   colliculocale
--------------------+-------------------
  testcoll_backwards | @colBackwards=yes
(1 row)

In the new cluster:
SELECT collname, colliculocale FROM pg_collation WHERE collname = 
'testcoll_backwards'
       collname      | colliculocale
--------------------+---------------
  testcoll_backwards |
(1 row)

diff_dump_colliculocale.patch works for me.

-- 
Marina Polyakova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Вложения

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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: handling multiple matching constraints in DetachPartitionFinalize()
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [BUG] parenting a PK constraint to a self-FK one (Was: Self FK oddity when attaching a partition)