Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xObJn-00000000EN6-0RwD for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Nov 2026 13:46:24 +0000 Received: from localhost ([127.0.0.1]:41148 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xObJn-00000006aEl-1VAG for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Nov 2026 13:46:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:34526) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xObJm-00000006aEd-1Uor for pgsql-bugs@lists.postgresql.org; Wed, 04 Nov 2026 13:46:23 +0000 Received: from fhigh-b7-smtp.messagingengine.com ([202.12.124.158]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xObJi-00000000DYQ-428W for pgsql-bugs@lists.postgresql.org; Wed, 04 Nov 2026 13:46:22 +0000 Received: from phl-compute-01.internal (phl-compute-01.internal [10.202.2.41]) by mailfhigh.stl.internal (Postfix) with ESMTP id BCE797A015A for ; Wed, 4 Nov 2026 08:46:15 -0500 (EST) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-01.internal (MEProxy); Wed, 04 Nov 2026 08:46:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eisentraut.org; h=cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1793799975; x=1793886375; bh=6maWtA6c+JEyQfCosS77xzLlRqhJ0XT6rAlCN2Gk4MA=; b= oMWLBfZ2oF/EFu255bSClomJ8Azm+ClWdIFQugyqllcPVtuhss4nEblXkL0b5nBg 4QiG0qzQh2T3Rlzqapsfh/nvev+esOUMJ//HHgRBC6NB7d1jMUHOIxmMXm82EbM4 5p+ML61TWDKqnkQLGAmpDdOIYeWV+gfAt8x4aOj1eEXfWgqGzmGqfKAivuG1lAPO TaPtefuPps3nRbWPTPzCiVXEMXTj6wW+aA62o5SDMhIuTCSnJo70Rbk7CTD77URT MNrFHR0xoO0S3m9LlWcvYuxkOIvFRfsQscJU0gOt8uqPPXoWcZG/48p7UBasxYos uffGS6kPiWN8fYdXnkBNmg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1793799975; x=1793886375; bh=6 maWtA6c+JEyQfCosS77xzLlRqhJ0XT6rAlCN2Gk4MA=; b=rA9Hm1vInnidbHOl0 bCLLfjeEtQuStwNiGYTWWP5aELLdnJlzrOGseS4LwhYNEKwzzqdfjEyh8jYeJC4W FnANLiKTyh/La1itiCvd5v9xTSsS3zde9a9ISI3DerUf24ZGHvP+ZObsvfMZUWNz MgH3VlvfL3KmTwDwBCL6UULmcHeiEEjit/v6AuU/9A1mII4O7WyB2m5aFQ7JSzJa 9+raPmG5fzLQzKdSMXT9o+7J6dF5flPGWkBVw8MF2g4pw3pL18ivMypowlGd5kQW 36YWi8mznKigBApaT3+IriBzhhQNmEfbbCU/TaGAYU30Kg/UP3LiabWg8SXiINOk 5QjWA== X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-08; repo=github.com/dkim2wg/interop; date=2026-10-28; sw=lmtpprox; action=sign d=eisentraut.org a=rsa-sha256; DKIM2-Signature: i=1; m=1; t=1793799975; d=eisentraut.org; mf=PHBldGVyQGVpc2VudHJhdXQub3JnPg==; rt=PHBnc3FsLWJ1Z3NAbGlzdHMucG9zdGdyZXNxbC5vcmc+; s=fm2:rsa-sha256:yG6uWqBBRCg3DRPu34835Odvy5IjkKjty7JGEw1eBvcCHUa 4LdVTscbYHHViWp4JqpT9TU6/QYNsxU9Bf1UxMLPT0tBRPzwlyKtcXCjzqXhSu/V +G1+ZzyoZ0wqQswd/ZshQRke8nM+pYtiRFCrBUJltzsc4H4Ulqxm06cZRUHhvdo8 mFV3e2z0XCByFDcfHNasx84TbzI1u/LkpGIxy1AVk2nio2lYinJRozMiUMmPIxgf QTO4B5ef/eVJbzTkb6E9XWzqKUPfed+4P/x/g0qg6r79lM+307mwZYXSBzz7LMy9 ikoGoDA5Lg9cL3Ldl+IpWZZwoP9gh0bXay4iY3Q==; X-DKIM2-Info: draft=ietf-dkim-dkim2-spec-08; repo=github.com/dkim2wg/interop; date=2026-10-28; sw=lmtpprox; action=mi-m=1; hc=13; hn=content-language,content-transfer-encoding,content-type,date, feedback-id,from,in-reply-to,message-id,mime-version,references, subject,to,user-agent; Message-Instance: m=1; h=sha256:OtwWnTzP9d0pmQYvGvTuWlZ/z1cTfRzixBTwjc8NY8E=:N5agoRp3tOAqulVJqWP7SJfMnx8QEbEd5YGpFsnVtDk=; X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: dmFkZTFPpoN1iKNCkx8+Ci/T0tKYM92N+MS88LkJI368ngoBccDYDLyfxyGlKqx2sJODLf UTB00Z+uqbh2FJT3/5A+E7vXxqc5yr+z+ZKhmEmu6FCnk3k6z0YatMWfzDolC9Asj48NUs 4mTieWvPn39Xiqrthv8m8p5waFNdid8h1GOG7o7oysyOnWjK7nPlRK5MvNXSA6UgBGfVWm /JL0YWBmWO+4gd4ZAM86y1MoiT+3LDneyiN3Jpbi5vmD8Mna83fZ6e/GWJbrHpMmq5kNCL 08hWaHtte26NZYmgjkGcX0S63jKcVVTXQabZTPjjybzUE2805kfbTdOyHde0J/EreDxJsr E3PsuFXrbfZ+NMpEPJWSm72eTELgmaExBhBh3qyzv1I1kqNpvGk5KEIQ6c+mYXdFHKoY81 ouWw7J+qdRoVAdUPzDz1Jb3fkWVWEwU4JE8rk0uHnYTWgIOluYoohphY5zntpebLwVE4nv EV2uZYWmiEHCPl5emMLLxM2oKkdpEV2Pq/qaqetdKvipD0SWF/KC8n/b+zHkZZOExk1XPA N64aaOvlJa7eLrMm/PNrB2Bd6KBiNwTBoX4WkKmHwTzqrCy9S/FPc4WQG2ZSSN9KfAF5QJ GFrHB3yHrRUpqyGaCwc4uvGjyOeXt6msgFQJpjDpzK1m+rryvJihi1lk8Inw X-ME-Proxy: Feedback-ID: ie0a040ee:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 4 Nov 2026 08:46:14 -0500 (EST) Message-ID: Date: Wed, 4 Nov 2026 14:46:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #19830: Mention that UNIQUE on a nondeterministic ICU collation treats ignorable characters as duplicates To: aswin.tummala@gmail.com, pgsql-bugs@lists.postgresql.org References: <19830-9825a04b0d6b4d60@postgresql.org> Content-Language: en-US From: Peter Eisentraut In-Reply-To: <19830-9825a04b0d6b4d60@postgresql.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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.