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 1xOQIs-000000008Ki-0l6W for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Nov 2026 02:00:43 +0000 Received: from localhost ([127.0.0.1]:34842 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xOQIs-000000036T1-2iMO for pgsql-bugs@arkaria.postgresql.org; Wed, 04 Nov 2026 02:00:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:33362) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xOQ2r-000000033Kv-0Xu1 for pgsql-bugs@lists.postgresql.org; Wed, 04 Nov 2026 01:44:09 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xOQ2o-000000007aN-1DFm for pgsql-bugs@lists.postgresql.org; Wed, 04 Nov 2026 01:44:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=PguKtjrBAqTw+KbsiqFdBHgSZKjEM/PC6rBZuzjEDQs=; b=GaeYuVKCbhFeLRFb8rkR3bQQ3e kQxvihWtSFC+ipn53aUX+wzbZGNQJNnXF5yJLHXNZZ+9FivS8Yv8kUOO08+GNFK6twpsbPgmB23zB kDfmefMZuFqjIyt283NN9W2CoucRaP11HloPShbK+NdtV80chc/gMU8ekFRDpBZA/YcB1bYDtzQWG 5Rg/H+Sfj5eBq90nVTkejajbjuRHasAd0bE8zvy011/TBiWWgzM8agSHeizmqvQutxsWCchNbdgp1 OBJ6nUjPy4vZexZbbL8wkrx5kosKEGoM3iM4xOVSZ9dFbX9jer6lJsoiHueByJmR3zRtxh6r+NpM7 A+j6bCaQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xOQ2l-00000000IlZ-3yiv for pgsql-bugs@lists.postgresql.org; Wed, 04 Nov 2026 01:44:04 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xOQ2k-00000000uWQ-2mlJ for pgsql-bugs@lists.postgresql.org; Wed, 04 Nov 2026 01:44:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19830: Mention that UNIQUE on a nondeterministic ICU collation treats ignorable characters as duplicates To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: aswin.tummala@gmail.com Reply-To: aswin.tummala@gmail.com, pgsql-bugs@lists.postgresql.org Date: Wed, 04 Nov 2026 01:43:34 +0000 Message-ID: <19830-9825a04b0d6b4d60@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19830 Logged by: aswini kumar tummala Email address: aswin.tummala@gmail.com PostgreSQL version: 19rc1 Operating system: Windows, MacOs Description: =20 Hi, =20 When migrating from SQL Server, we found that a UNIQUE constraint on a column with und-u-ks-level2 (deterministic =3D 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. =20 Reproduced on 18.6 and 19 RC1. =20 Thanks, Aswini Kumar Tummala