Re: BUG #14112: sorting v and w is broken with et_EE locate

Поиск
Список
Период
Сортировка
От Georg Kahest
Тема Re: BUG #14112: sorting v and w is broken with et_EE locate
Дата
Msg-id 5721E1D3.5010706@internet.ee
обсуждение исходный текст
Ответ на Re: BUG #14112: sorting v and w is broken with et_EE locate  (Thomas Munro <thomas.munro@enterprisedb.com>)
Список pgsql-bugs
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/28/2016 08:09 AM, Thomas Munro wrote:
> On Thu, Apr 28, 2016 at 4:43 PM, Thomas Munro
> <thomas.munro@enterprisedb.com> wrote:
>> On Thu, Apr 28, 2016 at 4:24 PM, Peter Geoghegan <pg@heroku.com>
>> wrote:
>>> On Wed, Apr 27, 2016 at 9:22 PM, Peter Geoghegan
>>> <pg@heroku.com> wrote:
>>>> On Wed, Apr 27, 2016 at 9:07 PM, Thomas Munro
>>>> <thomas.munro@enterprisedb.com> wrote:
>>>>> That does look odd.
>>>>
>>>> What happens if you replace the dot in each string with a
>>>> single 'x' character, Georg? Does the sort order look correct
>>>> to you then?
>>>
>>> I ask because I suspect that this might be the same strcoll()
>>> bug I describe here:
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1320356
>>>
>>> (In particular, see my remarks on Austria and Germany.)
>>
>> No change here.  This system has locales-all ("GNU C Library:
>> Precompiled locale data") package version 2.19-18+deb8u4 (and
>> same libc6).
>>
>> munro@yoga:~/junk$ LC_COLLATE=et_EE.utf8 sort < input a1.ee
>> vvbwjbln7.ee wwvl8.ee wxxezi6lkaq7eoi.ee vyz.ee
>> munro@yoga:~/junk$ LC_COLLATE=et_EE.utf8 sort < input2 a1xee
>> vvbwjbln7xee wwvl8xee wxxezi6lkaq7eoixee vyzxee
>
> Same result on a CentOS box.  I think the OP should probably write
> to bug-glibc-locales@gnu.org.
>


Hello,

Indeed the problem seems to be related to to glibc itself handling it
incorrectly.

Thank you for your time, ill report the bug to glibc.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJXIeHSAAoJEFDOdES6xIFjLNQP/3hLYCBS1ex78SN+uIZGT4xV
1nx/xadb9qQ3AoVT2CsHVgL9QVwCXmNbXR/tAfdj6OKy9i8WMzBvuI4cvZjKB+ei
f1FeJc2ldnpLgAQ9/R9FRqMpGch4MnkhwxhK4+c69TqTvugvPwGpSvAddPj5edxn
IM2diNuCtQKSw+fHwP1/N4hB67TfFX+rfoHbdhwSlGbuK8Lxs+kpxIecP1WutcS5
jrFbptaLlWKMTptQmyVKINu8sztRxMdlJ5ywUr9UpL2GdaQv3SzhzC5OOcDh4a96
stmh7fZ6DBBpvvGWg/bJLNTi+nOgyEb9vFwKQMvseyoXnyRG4JyvoNJyzDpccyVt
1lWYhnlPuSFTYOI9zWfhcmWgZ5XY7g3kC3B5Ode5pawvSsHZ1ynvsxEHOK9i3J67
nAU4g1ehjw9sYwl+5g7+xuRXNoGIAr4prGAzlM7ZOG+2mwEpAqaQGkxTYZ+Sts0i
I/+SIMpDfQbZmMjzkKvwBSAqJZlCZign1fEt234uhRuIfI3ucxhBAegXGFpUzQSS
/qy0knRog+ouTwQN3pV1QAbcHfC8ZcBiPSzivT3KNneHaD7usz2GrD8wB8OyAbMH
nzThOL6aUhLUdmCOpm9/zil4HTXcTWxSUcoWLhHEAjzlto+74I4yUJM7L5LK7Lfq
LWBpBv7i2Nj/goR2w2Ip
=Lfo9
-----END PGP SIGNATURE-----

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

Предыдущее
От: Francisco Olarte
Дата:
Сообщение: Re: BUG #14116: Character with value 0x0a must be escaped. using COPY FROM
Следующее
От: tushar
Дата:
Сообщение: alter table .. reset not throwing an error if storage_parameter name is wrong