Re: 010_database.pl fails on openbsd w/ LC_ALL=LANG=C

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 010_database.pl fails on openbsd w/ LC_ALL=LANG=C
Date: 2023-07-07 15:52:34
Message-ID: 15dc7f8fe8317456caafd2575e77def549e54cb3.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, 2023-07-02 at 09:56 -0700, Andres Freund wrote:
> #     expected: anything else
> [07:25:06.424](0.001s) not ok 7 - ICU-specific locale must be
> specified with ICU_LOCALE: error message
> [07:25:06.424](0.001s) #   Failed test 'ICU-specific locale must be
> specified with ICU_LOCALE: error message'
> #   at /home/postgres/postgres/src/test/icu/t/010_database.pl line
> 80.
> [07:25:06.424](0.000s) #                   'psql:<stdin>:2: NOTICE: 
> using standard form "und-u-ks-level1" for ICU locale
> "@colStrength=primary"'
> #     doesn't match '(?^:ERROR:  invalid LC_COLLATE locale name)'
> [07:25:06.425](0.000s) 1..7

[I apologize for the delay.]

The test is assuming that locale "@colStrength=primary" is valid for
ICU but invalid for libc. It seems that on that platform, setlocale()
is accepting it?

If some libc implementations are too permissive, I might need to just
disable this test. But if we can find a locale that is consistently
acceptable in ICU but invalid in libc, then I can keep it... perhaps
"und(at)colStrength=primary"?

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jehan-Guillaume de Rorthais 2023-07-07 15:58:59 Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key
Previous Message Jeff Davis 2023-07-07 15:42:01 Re: Fix search_path for all maintenance commands