Re: float4/float8/int64 passed by value with tsearch fixup - Mailing list pgsql-patches

From Tom Lane
Subject Re: float4/float8/int64 passed by value with tsearch fixup
Date
Msg-id 16113.1208650491@sss.pgh.pa.us
Whole thread Raw
In response to Re: float4/float8/int64 passed by value with tsearch fixup  (Zoltan Boszormenyi <zb@cybertec.at>)
Responses Re: float4/float8/int64 passed by value with tsearch fixup  (Zoltan Boszormenyi <zb@cybertec.at>)
List pgsql-patches
Zoltan Boszormenyi <zb@cybertec.at> writes:
>> That looks suspiciously locale-ish; what locale are you running PG in?

> hu_HU.UTF-8

Ah, and I'll bet zs sorts after zy in hu_HU.

The query is already doing an ORDER BY, so it's not at fault.  I think
the only thing we could do about this is add a variant expected file
with the hu_HU sort ordering.  I'd be happy to do that if it were
affecting the main regression tests, but not sure it's worth it for
contrib/tsearch2 ... thoughts?

            regards, tom lane

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: float4/float8/int64 passed by value with tsearch fixup
Next
From: Tom Lane
Date:
Subject: Re: float4/float8/int64 passed by value with tsearchfixup