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 1rpsEW-009CTf-St for pgsql-general@arkaria.postgresql.org; Thu, 28 Mar 2024 16:04:05 +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 1rpsEV-00Gm0Y-Nl for pgsql-general@arkaria.postgresql.org; Thu, 28 Mar 2024 16:04: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 1rpsEV-00Glxl-Cp for pgsql-general@lists.postgresql.org; Thu, 28 Mar 2024 16:04: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.94.2) (envelope-from ) id 1rpsES-0071LJ-Ac for pgsql-general@lists.postgresql.org; Thu, 28 Mar 2024 16:04: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 42SG3wJP3588878; Thu, 28 Mar 2024 12:03:58 -0400 From: Tom Lane To: Fire Emerald cc: pgsql-general@lists.postgresql.org Subject: Re: How to interpret 'depends on' errors in pg_restore? In-reply-to: <18e85c76c98.2815.a5aef60df33e8d2ac3d54c6545825f63@gmail.com> References: <18e84674c10.2815.a5aef60df33e8d2ac3d54c6545825f63@gmail.com> <3571436.1711634406@sss.pgh.pa.us> <18e85c76c98.2815.a5aef60df33e8d2ac3d54c6545825f63@gmail.com> Comments: In-reply-to Fire Emerald message dated "Thu, 28 Mar 2024 16:57:04 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3588876.1711641838.1@sss.pgh.pa.us> Date: Thu, 28 Mar 2024 12:03:58 -0400 Message-ID: <3588877.1711641838@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Fire Emerald writes: > The partitioning must be the problem somehow. [ shrug... ] You're still not providing any details that would let somebody else reproduce or diagnose the problem. https://wiki.postgresql.org/wiki/Guide_to_reporting_problems regards, tom lane