Re: [RRR] Tests citext casts
От | Tom Lane |
---|---|
Тема | Re: [RRR] Tests citext casts |
Дата | |
Msg-id | 22134.1226085338@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [RRR] Tests citext casts (Kenneth Marshall <ktm@rice.edu>) |
Ответы |
Re: [RRR] Tests citext casts
|
Список | pgsql-hackers |
Kenneth Marshall <ktm@rice.edu> writes: > Thank you for the pointers. lc_collate is set to en_US.UTF-8. I > re-initdb the database with the --no-locale option and then the > tests passed successfully. Thank you for the reminder that the > regression tests need to run against a C locale database. Actually, they don't expect that; all of the core regression tests pass under multiple locales. (I think there's even one variant file that's there specifically to make 'em pass in sv_SE ...) The reason for taking trouble over this is that "make installcheck" tests against an installed server, which quite likely isn't using C locale. Since the contrib modules are *only* testable in "make installcheck" fashion, this is actually a bigger consideration for them than for the core tests. In a quick test on a Fedora box, citext is the only core or contrib test that fails in en_US. (This is true in HEAD, even without having applied the proposed patch.) It would be good to clean that up. We could fix it by having multiple variant expected files for C and non-C locales, which is exactly what the core tests do. However, I'm loath to apply that approach when the citext test already has XML vs no-XML variants; we would then need two variant files per locale variant, which is a bit unreasonable from a maintenance standpoint. My inclination is to remove the XML-dependent citext tests, which don't seem especially useful, and then we can have whatever variants we need for locales. citext locale behavior seems much more interesting than testing whether it casts to xml or not. regards, tom lane
В списке pgsql-hackers по дате отправления: