Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1itxhh-0007Gr-F3 for pgsql-bugs@arkaria.postgresql.org; Tue, 21 Jan 2020 17:52:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1itxhf-0004Rp-JH for pgsql-bugs@arkaria.postgresql.org; Tue, 21 Jan 2020 17:52:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1itxhf-0004Ri-BM for pgsql-bugs@lists.postgresql.org; Tue, 21 Jan 2020 17:52:39 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1itxha-0005ls-Og for pgsql-bugs@lists.postgresql.org; Tue, 21 Jan 2020 17:52:38 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 00LHqTHK025914; Tue, 21 Jan 2020 12:52:29 -0500 From: Tom Lane To: mack@agilereasoning.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16222: [[:print:]] doesn't correctly handle Emoji skin tone modifiers on MacOS In-reply-to: <16222-35e7eba712c52525@postgresql.org> References: <16222-35e7eba712c52525@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Tue, 21 Jan 2020 17:16:16 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <25912.1579629149.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Tue, 21 Jan 2020 12:52:29 -0500 Message-ID: <25913.1579629149@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > On Linux heroku-18, these expressions both eval true: > select '✌'~'\A[[:print:]]*\Z'; > select '✌🏻'~'\A[[:print:]]*\Z'; > On MacOS Catalina, the 1st evals true but the 2nd evals false. This is entirely a function of what your operating system's locale support does. So it could be that you chose the wrong LC_CTYPE setting for the macOS database -- in C locale, for example, "false" is the right answer. However, we've observed that macOS's UTF8-based locales seem pretty brain-dead about handling of multibyte characters :-(. So it's likely that this boils down to being Apple's bug. I haven't detected any interest on their part in improving their POSIX locale support, unfortunately. regards, tom lane