Re: [PATCH] Run UTF8-dependent tests for citext [Re: daitch_mokotoff module]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dag Lem <dag(at)nimrod(dot)no>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Run UTF8-dependent tests for citext [Re: daitch_mokotoff module]
Date: 2022-01-05 18:38:42
Message-ID: 793161.1641407922@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dag Lem <dag(at)nimrod(dot)no> writes:
> Please find attached a patch to run the previously commented-out
> UTF8-dependent tests for citext, according to best practice. For now I
> don't dare to touch the unaccent module, which seems to be UTF8-only
> anyway.

I tried this on a bunch of different locale settings and concluded that
we need to restrict the locale to avoid failures: it falls over with
locale C. With that, it passes on all UTF8 LANG settings on RHEL8
and FreeBSD 12, and all except am_ET.UTF-8 on current macOS. I'm not
sure what the deal is with am_ET, but macOS has a long and sad history
of wonky UTF8 locales, so I was actually expecting worse. If the
buildfarm shows more problems, we can restrict it further --- I won't
be too upset if we end up restricting to just Linux systems, like
collate.linux.utf8. Anyway, pushed to see what happens.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-01-05 18:42:25 Re: [EXTERNAL] Re: PQcancel does not use tcp_user_timeout, connect_timeout and keepalive settings
Previous Message Zhihong Yu 2022-01-05 18:16:48 Re: [Proposal] Add foreign-server health checks infrastructure