Thread: Non-locale 7.1beta4 binaries on RedHat 6.2 test results.
Ok, after Tatsuo and Peter have both said that building without locale
support should not use the locale support in the OS, and remembering my
6.5.3 experience of a year back, I decided to test it out completely.
And I am wrong with respect to 7.1beta4.
For 7.1beta4 disabling locale will indeed work properly, at least on
RedHat 6.2.
Testing methodology:
1.) Blow out entire PGDATA tree;
2.) Initdb with locale-enabled backend;
3.) Run regression with locale-enable binaries (locale=en_US);
4.) Rebuild without --enable-locale;
5.) Blow out entire PGDATA tree;
6.) Initdb with non-locale backend;
7.) Run regression with non-locale binaries.
Results:
For --enable-locale RPM's, pg_regress --schedule=parallel_schedule
produces:
parallel group (13 tests): boolean char name varchar int4 int2 oid
float4 float
8 text bit int8 numeric boolean ... ok char ... ok name ... ok
varchar ... ok text ... ok int2 ... ok int4 ... ok
int8 ... FAILED oid ... ok float4 ... ok float8
...ok bit ... ok numeric ... FAILED
test strings ... ok
test numerology ... ok
parallel group (18 tests): point lseg box path polygon circle comments
reltime
date abstime interval time inet type_sanity tinterval timestamp oidjoins
opr_san
ity point ... ok lseg ... ok box ... ok path
... ok polygon ... ok circle ... ok date ... ok time
... ok timestamp ... ok interval ... ok abstime ... ok reltime
... ok tinterval ... ok inet ... ok comments ... ok oidjoins
... ok type_sanity ... ok opr_sanity ... ok
test geometry ... ok
test horology ... ok
test create_function_1 ... ok
test create_type ... ok
test create_table ... ok
test create_function_2 ... ok
test copy ... ok
parallel group (7 tests): create_aggregate create_operator triggers
inherit con
straints create_misc create_index constraints ... ok triggers ... ok create_misc
...ok create_aggregate ... ok create_operator ... ok create_index ... ok inherit
... ok
test create_view ... ok
test sanity_check ... ok
test errors ... ok
test select ... ok
parallel group (16 tests): select_into select_distinct_on
select_distinct selec
t_having select_implicit subselect transactions union case random arrays
aggrega
tes join portals hash_index btree_index select_into ... ok select_distinct ... ok
select_distinct_on ... ok select_implicit ... FAILED select_having ... FAILED subselect
... ok union ... ok case ... ok join ... ok aggregates
... ok transactions ... ok random ... failed (ignored) portals ... ok
arrays ... ok btree_index ... ok hash_index ... ok
test misc ... ok
parallel group (5 tests): portals_p2 alter_table rules foreign_key
select_views select_views ... FAILED alter_table ... ok portals_p2 ... ok rules
... ok foreign_key ... ok
parallel group (3 tests): limit temp plpgsql limit ... ok plpgsql ... ok temp
... ok
----
With locale disabled:
All 76 tests passed.
So, there's the data. This is different behavior from the 6.5.3
non-locale set I produced a year ago. Is there interest in a non-locale
RPM distribution, or? The locale enabled regression results fail due to
currency format and collation errors. Diffs attached. I'm not sure I
understand the select_views failure, either. Locale used was en_US.
Comments?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Lamar Owen <lamar.owen@wgcr.org> writes:
> The locale enabled regression results fail due to
> currency format and collation errors. Diffs attached. I'm not sure I
> understand the select_views failure, either. Locale used was en_US.
The select_views delta looks like a sort-order issue as well; nothing
to worry about.
These deltas would go away if you allowed pg_regress to build a temp
installation in which it could force the locale to C. Of course,
that doesn't presently work without a built source tree to install
from. I wonder if it is worth adding a third operating mode to
pg_regress that would build a temp PGDATA directory but use the
already-installed bin/lib/share directories ...
regards, tom lane
Tom Lane wrote: > Lamar Owen <lamar.owen@wgcr.org> writes: > > The locale enabled regression results fail due to > > currency format and collation errors. Diffs attached. I'm not sure I > > understand the select_views failure, either. Locale used was en_US. > The select_views delta looks like a sort-order issue as well; nothing > to worry about. Good. I didn't see any difference -- but maybe that's because I went cross-eyed.... :-) > These deltas would go away if you allowed pg_regress to build a temp > installation in which it could force the locale to C. Of course, > that doesn't presently work without a built source tree to install > from. I wonder if it is worth adding a third operating mode to Possibly. If pg_regress uses a different port for postmaster, AND a different PGDATA, you could run regression on a sandbox while a production system was running, FWIW. Since that's more of an RPM issue than a core issue, I can do that third mode work, as I would be the direct benefactor (unless someone else does it first, of course). Both the locale and non-locale installation were from RPM, BTW, as I wanted the least number of variables possible. -- Lamar Owen WGCR Internet Radio 1 Peter 4:11