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.94.2) (envelope-from ) id 1sJYUM-005XNw-6r for pgsql-general@arkaria.postgresql.org; Tue, 18 Jun 2024 13:03:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJYUJ-00Cltm-Ev for pgsql-general@arkaria.postgresql.org; Tue, 18 Jun 2024 13:03:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJYUJ-00Clt5-0P for pgsql-general@lists.postgresql.org; Tue, 18 Jun 2024 13:03:03 +0000 Received: from mout.gmx.net ([212.227.15.15]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJYUH-002Hpp-8P for pgsql-general@lists.postgresql.org; Tue, 18 Jun 2024 13:03:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.net; s=s31663417; t=1718715777; x=1719320577; i=karsten.hilbert@gmx.net; bh=5joUBgdjj6x0ZGVjmFkjZ7tYJNsOBucy1WrBZjYiRKk=; h=X-UI-Sender-Class:Date:From:To:Cc:Subject:Message-ID:References: MIME-Version:Content-Type:In-Reply-To:Content-Transfer-Encoding: cc:content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=HO9KJwikdTCSdAESYe6tNtrVmhQUcgL4rkT6STMparWL+hJhSv/Hitb9UP6jIlQx WjEa1UOzUmB8XbxQ0y1RCuqWLO/GRb+mCV3QPRavvZ/7zNrCup/k7LsvU1HS0LWdu BX1ft1wI4f7rcv+1fFBJCu95eBJtmtQ9vmXgYSwWQoWvkd+kZqrNtGph9VYwLKlSA yPjvYhAx1LM89AE8U7ZETwcmmG2w4UcSoFHcy01gSrd+dnA8GAa5jYFkZuZeh6ahh phbR7iy7KUq2p1v3IA71cLISjEcusxyiPNq4r1AOYj78CPhpEg8Z4D5Jzh7uPBuTS aw5edh+P32MCivv8Kg== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from hermes ([84.144.215.28]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MDQeK-1sCRDr1tt0-0094Ri; Tue, 18 Jun 2024 15:02:57 +0200 Received: from ncq by hermes with local (Exim 4.96) (envelope-from ) id 1sJYUC-0002Jx-1v; Tue, 18 Jun 2024 15:02:56 +0200 Date: Tue, 18 Jun 2024 15:02:56 +0200 From: Karsten Hilbert To: Tom Lane Cc: Laurenz Albe , pgsql-general@lists.postgresql.org Subject: Re: DROP COLLATION vs pg_collation question Message-ID: References: <26f717988471c4d672cce8c495a2c8e68446486a.camel@cybertec.at> <56da532b44bc02a7648796041ffa5da0a85c06df.camel@cybertec.at> <740fb9086af71f864ddb526cad1e55888385bedd.camel@cybertec.at> <3031360.1718570329@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3031360.1718570329@sss.pgh.pa.us> Ma_X_il-Followup-to: d Re_X_turn-receipt-to: Karsten.Hilbert@gmx.net Di_X_sposition-Notification-To: Karsten.Hilbert@gmx.net X-Confi_X_rm-Reading-To: Karsten.Hilbert@gmx.net X-Pri_X_ority: 2 (High) Sender: X-Provags-ID: V03:K1:6W6z4RBcybm851RpYaMYlS2R7Stxn4hHn5CDhrS/NRaa5s06Ehi 4v70zSUhtuVfvqicAhPs4w4uzrvKgykAuPVZ+1bBFCfg/EokZItARqMXADYRZqOYsMFfLs4 WJXoVVSN9ONPWl7RVV9ZZdQkdZyZMFr4d4OZ3It7JhP2YKuQ3kiWGfwvsvaUfRr0rLym9gT fzEOZ8VU1x5fxAYfTBXRA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:IGQA0H2AW2Y=;6wfxi3Hx17uHeKpZNvC2f6l4uqW crgoN9AGktu9k3wXJ88JYGY+h2irblgryBblo0VY9XxPZo3ix8s0T/bp2/fGZXudwQwvauqxV 2cIg6DKaq9cQMn4jXIXyZbrniytWGlc4595duZWsI1ntQu8VvZMcEjIbAJ7z9QQeNi83YsI5R YmHjeFCWWvFT6oM7e2B9KtloGlHOeErHmeSZs4DaYc5S/OaT2NYz4P8VwsXk66UGQ+a2SkZhs FuCMI0t5drefaveIVeCN9jFFCaXZ0kKs2KE8vlU8kt+BYYUYL2FfKAsVey0l0RMuZoUuv/PrC BMNEqMlaiIWXsWVaDRrwqx4ZdMgwemqGW880NGtMfMDTgEbkhZPOa4PlIvrWfT8glVY3niVm/ mA+haF5NkSCNFDe911D8+Jbl03O9TKzsFcDoFIKVTqZvCL5VtSxoELIJMN121apGtjWJwYoLs VGSavEJGu/ZsNvYumfnno8Up7cWiUCazWEWXHCAN/28ffJBzhn1DxtovFu5JNEH9IH4xBukCq olR7H+nux6Pv0h49sDNErBp3V9kPCfg5jn43qGg+YAna7ETvszVr1SOC4C20F/g70QbVWH/uV B4PcVgESNcjjltcWxw0moGityREfem1+NJccTnLt+ov2wJq+LOECns/PMYeSHnwO8R89b8E5q uptW3U4Hng2/Yu5vCpymwpr7Q8zJ/Z2HQABHpp5TyMH8rweO/rkes8dHMHrgNG57YbqehmEni 4I8FQ9tQdMySAw0zaXw03M4rzzRuz6G/JunNf6qWsg/wFlNV4yXDttmnIfTVub6d5ZJpZAiQW exI9OL27wsBKEFLU23IhfNNWz7teGtCD5cg/ct/tF6HLE= Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Am Sun, Jun 16, 2024 at 04:38:49PM -0400 schrieb Tom Lane: > It's really kind of moot, since you can't change the encoding > of an existing database. So any pg_collation entries that are > for an incompatible encoding cannot be used for anything in that > database, and they might as well not be there. The reason they > are there is merely an implementation detail: CREATE DATABASE clones > those catalogs from the single copy of pg_collation in template0, > which therefore had better include all collations that might be > needed. I see, and since any database can be used as a template for more databases, which can be create with an encoding different from the template, it doesn't really make too much sense to be able to remove even pg_collation entries. So, DROP COLLATION is somewhat of a smoking gun pointed at my foot :-) Thanks, Karsten =2D- GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B