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 1u2Z2k-002WeT-0d for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Apr 2025 17:16:54 +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 1u2Z2h-005j8e-F7 for pgsql-hackers@arkaria.postgresql.org; Wed, 09 Apr 2025 17:16:51 +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 1u2Z2h-005j8W-5M for pgsql-hackers@lists.postgresql.org; Wed, 09 Apr 2025 17:16:51 +0000 Received: from mail-yw1-x1136.google.com ([2607:f8b0:4864:20::1136]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1u2Z2e-004NMa-3A for pgsql-hackers@lists.postgresql.org; Wed, 09 Apr 2025 17:16:51 +0000 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-6febf391132so64779027b3.1 for ; Wed, 09 Apr 2025 10:16:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1744219007; x=1744823807; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=JFct1TWXO7KirQEiUepT+UJWBMYUuVCFhPuQl8lOsWE=; b=CUw5NA7PJHEVGfM6q66XcR7T3PYrAvu2qrVdFAuxDRX6uObTrarNEOg+D9HrQBQYGG 9EGHAgyNxNxcgJUwe3/KegdmnamSwXXNii4xfIGnjG5trmvdUrXW7wXdhuKNwqrd/1R5 kCVGPIHOeRPJkuJnCCytGZ1689WGjA0IqpnKsrEi6CSAihQHQUIcm+mIhtsAXTokynjN KkCS+E6YBfT99Ql9aOE8WngSjNMDOPXVJ7gwN+bAltZ+6ywk5bOFn39kLZOtF/oehWel HbEDKejorzDvsgaItCjSGNq6mfhiL1OlumMZxmF+kw9o4Z3RgOwRM6hUyiPXUX68HcUs ihTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1744219007; x=1744823807; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=JFct1TWXO7KirQEiUepT+UJWBMYUuVCFhPuQl8lOsWE=; b=Xm9nCjADgf4cXpLP1Ie2qrFCOCS6JrlDFnqyLMQZr7t60VsYR/5UWsNMGx6ZnDK0Al IWbKvOvDNXE0L2ywPRCBOwQvNsXlXke+48h7/3XILyrEUMZk8vghTHRFO0x11fPDUWiX QQLx6AR7Qv2RXGWaUsksVf7r1q7D4gQLLDHhJlHqt7jlSRQC+8MKZdWp74y/u/DyJPpH 7jd98r/FCe+JnZsDZyJ+uZlnpZ0T226bMv2In6OL1cik+/JRIOeVi2MgTsOP/tOy3zL7 4KIWFW9E2gzt2iYxgx5HeJ3OLwYZAMZiIvqnWTkkXP2pkuszbcpMjfXZ+okJhvoqTEeW eZTQ== X-Forwarded-Encrypted: i=1; AJvYcCU9l3ns2zEWVageQZKczg3fJE7u++SEBMKGMuvApUhzU73ZwUEV8623/qlm/zchBlCBTgFnH2famlPUTGDJ@lists.postgresql.org X-Gm-Message-State: AOJu0Yz5CbeTA+lTpANO8rZ3DOz6x9FHd/ujCPabOLwNuqM35gNHezoV vPBJn7vwsQZQIW/vygVEK8DLKl/xF+HdBsnErI0u0mx1L97hxq/1nZR8ow== X-Gm-Gg: ASbGncuN4vyeKngfgFq2dbbTP7jG4KoSpqwZhZmbE/nwkSWgPWeDFN/u5vXkSX0F4NG y2RAAChrxv8oNhNs/ix+ZqhQC2ZEza+nv9PvnU0cQZ63PrRCjTGQ7e39sSKuxxl5Jo6SaZvfL2T 4F3/s3ZkdWwrb9K5SI/DJ9LLMce7R7vHi1etfEZoGIqYs2KoFkZMeMDI4fOlWXTdtipRkhWu+1q 1tJo1FUhZpmBQtM+CNJuLmdZ+GlI3Q3/AmVozKDFi5KaG4GGmHuBhuf2ygeyq2DRF8viFlzGBt2 f/VxxMGVFwjVmnyV0OytNBn0q1ywOLD4Y9uIT0r+9Vjeb2qA0ilLxpFq+BSZvQcvlh0t0z9W5HS SkvuL/NOqY2OuEFgMHLiKvWnDIIYsXhc= X-Google-Smtp-Source: AGHT+IEM8zoMalIEwis3wMzw9ige8TlVOewPjaZvxl0YsGgRyEKbsulVWHW70yniVFBttJrXWgcarw== X-Received: by 2002:a05:690c:630e:b0:702:627e:a787 with SMTP id 00721157ae682-705388d8f84mr64135667b3.29.1744219006851; Wed, 09 Apr 2025 10:16:46 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id 00721157ae682-7053e11d349sm3565877b3.43.2025.04.09.10.16.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Apr 2025 10:16:46 -0700 (PDT) Date: Wed, 9 Apr 2025 12:16:44 -0500 From: Nathan Bossart To: Tom Lane Cc: Hannu Krosing , PostgreSQL Hackers Subject: Re: Horribly slow pg_upgrade performance with many Large Objects Message-ID: References: <4044567.1744128814@sss.pgh.pa.us> <4047312.1744130263@sss.pgh.pa.us> <4050387.1744132029@sss.pgh.pa.us> <4054389.1744133818@sss.pgh.pa.us> <4055696.1744134682@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2Cj/f6XvWUd4DfY2" Content-Disposition: inline In-Reply-To: <4055696.1744134682@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --2Cj/f6XvWUd4DfY2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 08, 2025 at 01:51:22PM -0400, Tom Lane wrote: > Nathan Bossart writes: >> On Tue, Apr 08, 2025 at 01:36:58PM -0400, Tom Lane wrote: >>> 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. > >> I think it does; see commit aa01051. > > Ah --- I thought I remembered something having been done about that, > but I failed to find it because I was looking in pg_upgrade not > pg_dump. Too bad aa01051 didn't update the comment at the top of > pg_upgrade.c. I'll apply the attached patch to fix the comment shortly. -- nathan --2Cj/f6XvWUd4DfY2 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="v1-0001-Mention-that-we-preserve-database-OIDs-in-pg_upgr.patch"