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 1rpqIf-008wfk-Oq for pgsql-general@arkaria.postgresql.org; Thu, 28 Mar 2024 14:00:14 +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 1rpqIe-00EhmY-3y for pgsql-general@arkaria.postgresql.org; Thu, 28 Mar 2024 14:00:12 +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 1rpqId-00EhmQ-PA for pgsql-general@lists.postgresql.org; Thu, 28 Mar 2024 14:00:11 +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 1rpqIb-0070K9-1S for pgsql-general@lists.postgresql.org; Thu, 28 Mar 2024 14:00:11 +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 42SE06HM3571437; Thu, 28 Mar 2024 10:00:06 -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: <18e84674c10.2815.a5aef60df33e8d2ac3d54c6545825f63@gmail.com> References: <18e84674c10.2815.a5aef60df33e8d2ac3d54c6545825f63@gmail.com> Comments: In-reply-to Fire Emerald message dated "Thu, 28 Mar 2024 10:32:26 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3571435.1711634406.1@sss.pgh.pa.us> Date: Thu, 28 Mar 2024 10:00:06 -0400 Message-ID: <3571436.1711634406@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Fire Emerald writes: > Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the > output this: > 5145 0 730750 TABLE subpartitions backends_y2024w03 userA > ; depends on: 237 > .... and so on ... That is not an error, it's just verbose display of one of the items in the dump. > Nothing was restored. You would need to show us the actual errors. (Suggestion: leave off --verbose, it's just clutter.) A guess though is that the import failed because of foreign key constraints. --data-only mode is not good at ordering the table loads to ensure that FK constraints are satisfied on-the-fly. regards, tom lane