From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Marco Atzeri <marco(dot)atzeri(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Postgresql for cygwin - 3rd |
Date: | 2014-02-01 22:46:25 |
Message-ID: | 16213.1391294785@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 02/01/2014 05:12 PM, Marco Atzeri wrote:
>> is it possible the tsearch test never worked on en_US.utf8
>> but only on C locale ?
> Yes, that's more or less what I said, I thought.
> Maybe we need to test this on other Windows systems in non-C encodings.
> Let's make sure it's only a Cygwin problem.
> I'll work on that. You should try to concentrate on the thinks like
> prepared_xacts and isolation_test that we know don't work ONLY on Cygwin.
Please test the patch I just posted in the pgsql-bugs thread. It looks
to me like there are bugs in both the C and non-C locale cases, but only
the latter case would be exercised by our regression tests, since we
don't use any non-ASCII characters in the tests.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-02-01 23:13:42 | Re: jsonb and nested hstore |
Previous Message | Andrew Dunstan | 2014-02-01 22:38:06 | Re: Postgresql for cygwin - 3rd |