| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: how to run encoding-dependent tests by default |
| Date: | 2019-07-29 05:34:39 |
| Message-ID: | 211375f3-f2eb-68f3-6813-eb51f9869d7a@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-07-28 21:42, Tom Lane wrote:
> Oh ... one other thought, based on forcing the collate.linux.utf8
> test to run on platforms where it can be expected to fail: I think
> you'd be well advised to make that test verify that the required
> collations are present, the same as you did in the collate.icu.utf8
> test. I noticed for instance that it fails if en_US.utf8 is not
> present (or not spelled exactly like that), but I doubt that that
> locale is necessarily present on every Linux platform. tr_TR is
> even more likely to be subject to packagers' whims.
This was already done in my v2 test posted in this thread.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2019-07-29 05:52:48 | Re: Duplicated LSN in ReorderBuffer |
| Previous Message | Peter Eisentraut | 2019-07-29 05:34:07 | Re: how to run encoding-dependent tests by default |