pgsql: Fix varstr_cmp's special case for UTF8 encoding on Windows so

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix varstr_cmp's special case for UTF8 encoding on Windows so
Date: 2008-03-13 18:32:02
Message-ID: 20080313183202.8AD27753C45@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix varstr_cmp's special case for UTF8 encoding on Windows so that strings
that are reported as "equal" by wcscoll() are checked to see if they really
are bitwise equal, and are sorted per strcmp() if not. We made this happen
a couple of years ago in the regular code path, but it unaccountably got
left out of the Windows/UTF8 case (probably brain fade on my part at the
time). As in the prior set of changes, affected users may need to reindex
indexes on textual columns.

Backpatch as far as 8.2, which is the oldest release we are still supporting
on Windows.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
pgsql/src/backend/utils/adt:
varlena.c (r1.162 -> r1.162.2.1)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c?r1=1.162&r2=1.162.2.1)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-03-13 18:32:09 pgsql: Fix varstr_cmp's special case for UTF8 encoding on Windows so
Previous Message Tom Lane 2008-03-13 18:31:56 pgsql: Fix varstr_cmp's special case for UTF8 encoding on Windows so