Re: foreign_data test fails with non-C locale

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Cc: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: foreign_data test fails with non-C locale
Date: 2009-01-31 22:08:15
Message-ID: 4984CBCF.1040703@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zdenek Kotala wrote:
>> PL-check gives the diff below on PLTCL tests under en_US locale. I guess
>> the simplest answer is to add an alternative result file.
>>
>
> Yes, I thought about add locale suffix for alternative result file, but
> it could be useless overhead.
>
> But some tests can be modified. For example
>
> select * from T_pkey1 order by key1 using @<, key2;
>
> can be rewritten as
>
> select * from T_pkey1 order by key1 using @<, key2::name;
>
>
>
>

Is that the preferred solution? I want to fix this so I can re-enable
building with TCL in dungbeetle.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2009-01-31 22:28:15 LIMIT NULL
Previous Message Robert Haas 2009-01-31 21:21:30 Re: [PATCH] Space reservation v02