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 1p3LeT-0008Ko-Qr for pgsql-bugs@arkaria.postgresql.org; Thu, 08 Dec 2022 18:29:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p3LeS-0006wy-9b for pgsql-bugs@arkaria.postgresql.org; Thu, 08 Dec 2022 18:29:44 +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 1p3LeR-0006wp-6T for pgsql-bugs@lists.postgresql.org; Thu, 08 Dec 2022 18:29:44 +0000 Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3LeM-00040g-FC for pgsql-bugs@lists.postgresql.org; Thu, 08 Dec 2022 18:29:42 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailnew.nyi.internal (Postfix) with ESMTP id 39BC05803E8; Thu, 8 Dec 2022 13:29:35 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Thu, 08 Dec 2022 13:29:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1670524175; x= 1670531375; bh=E478PzErxpaac/itKSfP0QPUqjMYWTCDGJC3K9aFajM=; b=v 1QUOPDz/cwUAwwuSq2MbaQZgJWkPTF1dG+V9FD4qcTn9B+nEzOFSmGV0dAeCdRSY T1+VDozmlzHC05kztYtZ45vZqCUi8unvmP5wII2i/WSPHR/aZy2ZTIcClH8d317v gClUPWQvdKVhlpgqRVJD6bGBdP2bpnMcrPf/cxaNQKuB0KvZOF8+YPP9r9Aff6r0 99Qps+U5aZLMcQ+XYx3gH6buHV6nZU9b3yGYEvoc4I+1yWFSLuHCuJ4Q2jzYg3JQ rIGz5Ik4LKCH5Ksbvb8WybYD440jbPtfBZKB3mrxUsJSm29fsJPoP4e/P8Nxlcao Fqmn8+B/Dk2AXmgaNvdJg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvddtgdduudegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpefhjeduueelfeehuedt udefteejveegieeiueejueehfeektddtueeiieeitefhveenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 8 Dec 2022 13:29:33 -0500 (EST) Message-ID: <38ab220b-83a7-17a4-42b1-923a5f96ef15@enterprisedb.com> Date: Thu, 8 Dec 2022 19:29:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Subject: Re: CREATE COLLATION without LOCALE throws error in v15 Content-Language: en-US To: Jeff Davis , Kyle Spearrin , pgsql-bugs@lists.postgresql.org Cc: Justin Baur , Vince Grassia References: <7b99b4a7fc5284008bae32b77a776d25b4a400bc.camel@j-davis.com> <428169fe-2eb3-4415-a5be-6f59112f26b2@enterprisedb.com> <69598b5a07183ea8c6ec20826c1b549db1128070.camel@j-davis.com> From: Peter Eisentraut In-Reply-To: <69598b5a07183ea8c6ec20826c1b549db1128070.camel@j-davis.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 07.12.22 18:44, Jeff Davis wrote: > On Wed, 2022-12-07 at 13:04 +0100, Peter Eisentraut wrote: >> This was an intentional change because of underlying conceptual and >> catalog changes.  lc_collate, lc_ctype, and iculocale are now tracked >> separately in the catalogs.  This is also important because for a >> database they actually are used separately.  So this also keeps the >> locale/collation settings for databases and collations consistent. > > That makes sense, but there also doesn't seem to be much harm in > supporting the old behavior where it works as long as ctype==collate. > As in my patch, it accepts either locale or ctype==collate as the icu > locale. The harm is that in the context of database-level collations, the analogous syntax means something different. That's why in the context of adding ICU support on the database level, this syntax for collation objects was disabled.