pgsql: Allow unrecognized encoding names in locales, as long as they're - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Allow unrecognized encoding names in locales, as long as they're
Date
Msg-id E1W988y-0000mx-Hs@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Allow unrecognized encoding names in locales, as long as they're the same.

The buildfarm says commit 58274728fb8e087049df67c0eee903d9743fdeda doesn't
work so well on Windows.  This is because the encoding part of Windows
locale names can be just a code page number, eg "1252", which we don't
consider to be a valid encoding name.  Add a check to accept encoding
parts that are case-insensitively string equal; this at least ensures
that the new code doesn't reject any cases that the old code allowed.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/cd3e0071b8c9e082f5fe903a019d4e474be98e57

Modified Files
--------------
contrib/pg_upgrade/check.c |   10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Bruce Momjian
Date:
Subject: pgsql: pgindent: preserve blank lines around #else/#endif
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: pgsql: Add json_array_elements_text function.