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

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix psql's copy of utf2ucs() to match the backend's copy exactly;
Date: 2010-08-16 00:07:01
Message-ID: 20100816000701.09DEF7541D7@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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:
----
REL7_4_STABLE

Modified Files:
--------------
pgsql/src/bin/psql:
mbprint.c (r1.12 -> r1.12.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/mbprint.c?r1=1.12&r2=1.12.2.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2010-08-16 02:02:28 pgsql: Make LockDatabaseObject() AcceptInvalidationMessages().
Previous Message Tom Lane 2010-08-16 00:06:54 pgsql: Fix psql's copy of utf2ucs() to match the backend's copy exactly;