On Sun, 2011-10-16 at 16:00 -0400, Tom Lane wrote:
> Jeff Davis <[email protected]> writes:
> > On master, I see a minor test error (at least on my machine) as well as
> > a diff. Patch attached.
>
> Hmm, yeah, I forgot to fix this regression test when I added that DETAIL
> line. However, I don't see the need for fooling with the lc_time value?
>
> regards, tom lane
Here is the diff that I'm seeing on master right now with:
make -s check EXTRA_TESTS=collate.linux.utf8
If I qualify it as "tr_TR.UTF-8" it works. Perhaps I have something
misconfigured on my system (Ubuntu 11.10)? I just installed:
language-pack-de
language-pack-tr
language-pack-sv
in an attempt to make the test work, and it works all except for that
lc_time settng.
Regards,
Jeff Davis
*** /home/jdavis/wd/git/postgresql/src/test/regress/expected/collate.linux.utf8.out 2011-10-18 00:47:06.817223853 -0700
--- /home/jdavis/wd/git/postgresql/src/test/regress/results/collate.linux.utf8.out 2011-10-18 01:02:06.509206748 -0700
***************
*** 396,411 ****
-- to_char
SET lc_time TO 'tr_TR';
SELECT to_char(date '2010-04-01', 'DD TMMON YYYY');
to_char
-------------
! 01 NIS 2010
(1 row)
SELECT to_char(date '2010-04-01', 'DD TMMON YYYY' COLLATE "tr_TR");
to_char
-------------
! 01 NİS 2010
(1 row)
-- backwards parsing
--- 396,412 ----
-- to_char
SET lc_time TO 'tr_TR';
+ ERROR: invalid value for parameter "lc_time": "tr_TR"
SELECT to_char(date '2010-04-01', 'DD TMMON YYYY');
to_char
-------------
! 01 APR 2010
(1 row)
SELECT to_char(date '2010-04-01', 'DD TMMON YYYY' COLLATE "tr_TR");
to_char
-------------
! 01 APR 2010
(1 row)
-- backwards parsing
======================================================================
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
