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 1pWhrP-0006oU-FJ for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Feb 2023 18:04: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 1pWhrO-0002fj-0y for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Feb 2023 18:04:26 +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 1pWhrN-0002fa-Np for pgsql-hackers@lists.postgresql.org; Mon, 27 Feb 2023 18:04:25 +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 1pWhrL-0003Su-Lu for pgsql-hackers@lists.postgresql.org; Mon, 27 Feb 2023 18:04:25 +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 31RI4GWl391721; Mon, 27 Feb 2023 13:04:16 -0500 From: Tom Lane To: Robert Haas cc: Andrew Dunstan , Alvaro Herrera , David Rowley , Peter Geoghegan , pgsql-hackers@lists.postgresql.org, Andrew Subject: Re: pg_dump versus hash partitioning In-reply-to: References: <1376149.1675268279@sss.pgh.pa.us> <1412538.1675283692@sss.pgh.pa.us> <1425446.1675291093@sss.pgh.pa.us> <1440373.1675299790@sss.pgh.pa.us> <1533086.1675349554@sss.pgh.pa.us> <1912821.1676402493@sss.pgh.pa.us> <369734.1677514834@sss.pgh.pa.us> <389892.1677520215@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Mon, 27 Feb 2023 12:55:01 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <391719.1677521056.1@sss.pgh.pa.us> Date: Mon, 27 Feb 2023 13:04:16 -0500 Message-ID: <391720.1677521056@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Haas writes: > Sure, but I was responding to your assertion that there's no case in > which --load-via-partition-root could cause a restore failure. I'm not > sure that's accurate. Perhaps it's not, but it's certainly far less likely to cause a restore failure than the behavior I want to replace. More to the current point perhaps, I doubt that it's likely enough to cause a restore failure to justify the existing docs warning. There may have been a time when the warning was justified, but I don't believe it today. regards, tom lane