Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oN6um-000383-0J for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Aug 2022 06:16:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oN6uk-0001NJ-4y for pgsql-bugs@arkaria.postgresql.org; Sun, 14 Aug 2022 06:15:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oN6uj-0001N9-Sn for pgsql-bugs@lists.postgresql.org; Sun, 14 Aug 2022 06:15:57 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oN6ud-0000W3-EI for pgsql-bugs@lists.postgresql.org; Sun, 14 Aug 2022 06:15:56 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 27E6FjhB587802; Sun, 14 Aug 2022 02:15:46 -0400 From: Tom Lane To: Peter Geoghegan cc: James Inform , PostgreSQL mailing lists , Euler Taveira Subject: Re: BUG #17584: SQL crashes PostgreSQL when using ICU collation In-reply-to: <559703.1660450255@sss.pgh.pa.us> References: <17584-95c79b4a7d771f44@postgresql.org> <465044.1660428315@sss.pgh.pa.us> <92087cd5-5410-a4e9-41fe-4ff310439190@pharmapp.de> <541938.1660437017@sss.pgh.pa.us> <555147.1660447264@sss.pgh.pa.us> <559703.1660450255@sss.pgh.pa.us> Comments: In-reply-to Tom Lane message dated "Sun, 14 Aug 2022 00:10:55 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <587800.1660457745.1@sss.pgh.pa.us> Date: Sun, 14 Aug 2022 02:15:45 -0400 Message-ID: <587801.1660457745@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ... BTW, I wondered how come we'd missed noticing such a serious problem in any testing. The code coverage report at https://coverage.postgresql.org/src/backend/utils/adt/varlena.c.gcov.html says that only the "if (sss->collate_c)" path in varstr_abbrev_convert gets exercised in our regression tests. I thought maybe that just meant that the coverage.postgresql.org run uses C locale, but I see the same lack-of-coverage in a local test under LANG=en_US.utf8. How can we only be reaching this function with sss->collate_c true when the prevailing locale isn't that? regards, tom lane