character_not_in_repertoire vs. untranslatable_character - Mailing list pgsql-hackers

From Chapman Flack
Subject character_not_in_repertoire vs. untranslatable_character
Date
Msg-id 56DC6FBD.3030807@anastigmatix.net
Whole thread Raw
Responses Re: character_not_in_repertoire vs. untranslatable_character
List pgsql-hackers
So there's an ISO error 22021 "character not in repertoire" and
a PostgreSQL error 22P05 "untranslatable character" that seem
very similar.

If I look in backend/utils/mb/wchar.c, it looks as if PostgreSQL
uses the first for the case of a corrupted encoding (bytes that
can't be decoded to a character at all), and the second for the
case of a valid character that isn't available in a conversion's
destination encoding.

Am I right about that? The names seem sort of confusable, and even
reading ISO 9075 drafts I haven't really found any additional detail
on what they wanted 22021 to mean, so I guess as long as I know what
it means in PG, that's as good as it gets. :)

-Chap



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: WIP: Upper planner pathification
Next
From: Euler Taveira
Date:
Subject: Re: pg_basebackup compression TODO item