pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter@eisentraut.org>
To: aswin.tummala@gmail.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19830: Mention that UNIQUE on a nondeterministic ICU collation treats ignorable characters as duplicates
Date: Wed, 4 Nov 2026 14:46:13 +0100
Message-ID: <ae1fcac5-5f42-4e75-939d-a42be94472c4@eisentraut.org> (raw)
In-Reply-To: <19830-9825a04b0d6b4d60@postgresql.org>
References: <19830-9825a04b0d6b4d60@postgresql.org>

On 04.11.26 02:43, PG Bug reporting form wrote:
>    When migrating from SQL Server, we found that a UNIQUE constraint on a
> column with und-u-ks-level2 (deterministic = false)
>    rejects 'ACME' || U&'\200B' as a duplicate of 'ACME'. The same data loads
> fine into a citext column. Section 23.2.3.1 does show
>    U+2063 being ignored, but it doesn't say what that means for constraints.
> A short note under "Nondeterministic Collations" would
>    have saved us time. It could say that ignorable code points (zero-width
> space, soft hyphen, BOM, most control characters) don't
>    count toward uniqueness, and that this differs from citext.

What you are observing is a very specific combination of several 
features.  It would be extremely niche and redundant to document this 
particular case.

I would think that if you understand what nondeterministic collations 
are (and you have chosen to use them) and you know what unique 
constraints are, then this behavior would follow from that.  We could 
perhaps try to clarify this somehow, but it would have to be in more 
general terms.







view thread (2+ messages)

Message-ID: <ae1fcac5-5f42-4e75-939d-a42be94472c4@eisentraut.org>
Permalink:  ../ae1fcac5-5f42-4e75-939d-a42be94472c4@eisentraut.org/
Also on:    postgresql.org/message-id/ae1fcac5-5f42-4e75-939d-a42be94472c4@eisentraut.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: peter@eisentraut.org, aswin.tummala@gmail.com
  Subject: Re: BUG #19830: Mention that UNIQUE on a nondeterministic ICU collation treats ignorable characters as duplicates
  In-Reply-To: <ae1fcac5-5f42-4e75-939d-a42be94472c4@eisentraut.org>
  References: <19830-9825a04b0d6b4d60@postgresql.org> <ae1fcac5-5f42-4e75-939d-a42be94472c4@eisentraut.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox