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 1u2Csi-00Eg6Z-Kc for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Apr 2025 17:37:04 +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 1u2Csh-00D5Yb-3H for pgsql-hackers@arkaria.postgresql.org; Tue, 08 Apr 2025 17:37:03 +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 1u2Csg-00D5YS-QA for pgsql-hackers@lists.postgresql.org; Tue, 08 Apr 2025 17:37:03 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1u2Cse-004B9G-30 for pgsql-hackers@lists.postgresql.org; Tue, 08 Apr 2025 17:37:02 +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 538HawLd4054390; Tue, 8 Apr 2025 13:36:58 -0400 From: Tom Lane To: Hannu Krosing cc: Nathan Bossart , PostgreSQL Hackers Subject: Re: Horribly slow pg_upgrade performance with many Large Objects In-reply-to: References: <4044567.1744128814@sss.pgh.pa.us> <4047312.1744130263@sss.pgh.pa.us> <4050387.1744132029@sss.pgh.pa.us> Comments: In-reply-to Hannu Krosing message dated "Tue, 08 Apr 2025 19:18:31 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4054388.1744133818.1@sss.pgh.pa.us> Date: Tue, 08 Apr 2025 13:36:58 -0400 Message-ID: <4054389.1744133818@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hmm ... one annoying thing for this project is that AFAICS pg_upgrade does *not* preserve database OIDs, which is problematic for using COPY to load pg_shdepend rows. regards, tom lane