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 1nWMuF-0006SL-IT for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Mar 2022 18:37:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nWMuD-0000aO-3u for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Mar 2022 18:37:25 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWMuC-0000aE-R3 for pgsql-hackers@lists.postgresql.org; Mon, 21 Mar 2022 18:37:24 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWMuA-0001Zs-H1 for pgsql-hackers@lists.postgresql.org; Mon, 21 Mar 2022 18:37:24 +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 22LIbCjS2158267; Mon, 21 Mar 2022 14:37:12 -0400 From: Tom Lane To: Christoph Berg cc: Peter Eisentraut , pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Add option to use ICU as global locale provider In-reply-to: References: <2298daf1-c9c7-be30-7319-519a768b9405@enterprisedb.com> Comments: In-reply-to Christoph Berg message dated "Mon, 21 Mar 2022 17:59:56 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2158265.1647887832.1@sss.pgh.pa.us> Date: Mon, 21 Mar 2022 14:37:12 -0400 Message-ID: <2158266.1647887832@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Christoph Berg writes: > A possible solution might be to rip out all the locale columns except > "Encoding" from \l, and leave them in place for \l+. I'd rather see a single column summarizing the locale situation. Perhaps it could be COALESCE(daticulocale, datcollate), or something using a CASE on datlocprovider? Then \l+ could replace that with all the underlying columns. > For \l+, I'd suggest moving the database size and the tablespace to > the front, after owner. I think it's confusing if the + and non-+ versions of a command present their columns in inconsistent orders. I'm not dead set against this, but -0.5 or so. regards, tom lane