pgsql: Fix psql's copy of utf2ucs() to match the backend's copy exactly; - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix psql's copy of utf2ucs() to match the backend's copy exactly;
Date
Msg-id 20100816000624.EB8497541D7@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix psql's copy of utf2ucs() to match the backend's copy exactly;
in particular, propagate a fix in the test to see whether a UTF8 character has
length 4 bytes.  This is likely of little real-world consequence because
5-or-more-byte UTF8 sequences are not supported by Postgres nor seen anywhere
in the wild, but still we may as well get it right.  Problem found by Joseph
Adams.

Bug is aboriginal, so back-patch all the way.

Tags:
----
REL9_0_STABLE

Modified Files:
--------------
    pgsql/src/bin/psql:
        mbprint.c (r1.38 -> r1.38.6.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/mbprint.c?r1=1.38&r2=1.38.6.1)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Assorted improvements to backup/restore documentation, per Thom
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix psql's copy of utf2ucs() to match the backend's copy exactly;