Skip site navigation (1) Skip section navigation (2)

Re: float4/float8/int64 passed by value with tsearch fixup

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zoltan Boszormenyi <zb(at)cybertec(dot)at>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-patches(at)postgresql(dot)org, Hans-Juergen Schoenig <hs(at)cybertec(dot)at>, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: float4/float8/int64 passed by value with tsearch fixup
Date: 2008-04-20 00:14:51
Message-ID: 16113.1208650491@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
Zoltan Boszormenyi <zb(at)cybertec(dot)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

In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2008-04-20 01:06:47
Subject: Re: float4/float8/int64 passed by value with tsearchfixup
Previous:From: Tom LaneDate: 2008-04-20 00:03:32
Subject: Re: float4/float8/int64 passed by value with tsearch fixup

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group