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 1sp96L-00GyId-5C for pgsql-admin@arkaria.postgresql.org; Fri, 13 Sep 2024 16:24: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 1sp96K-006dR7-IW for pgsql-admin@arkaria.postgresql.org; Fri, 13 Sep 2024 16:24:52 +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 1sp96K-006dQy-0u for pgsql-admin@lists.postgresql.org; Fri, 13 Sep 2024 16:24:52 +0000 Received: from mout-u-204.mailbox.org ([80.241.59.204]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sp96C-00110D-Qn for pgsql-admin@lists.postgresql.org; Fri, 13 Sep 2024 16:24:51 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [IPv6:2001:67c:2050:b231:465::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-204.mailbox.org (Postfix) with ESMTPS id 4X505520vxz9sWx; Fri, 13 Sep 2024 18:24:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1726244681; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4iMRMcK61TQj1lLkCkKJMvsm/1A4ZOYTsXbozQCJJSc=; b=TdF9G46+JzXavhsB796u3NkAcmwqy6v2PACvBvABhLI6QAiwL7FAS5i5ZYtJQS93Dz29S+ AKBGNdQT2GjOZMgVFYz5LhnRsxgd+WHP7Ynq0WwcEEfH0XFrxojzOgFw3u/+d0DiWHKeeH W2jC8SF5ZKmGasEznzsxzpgBCQQEnxLRkPt33EvniFrAUStZboUtXaJImmoATvf/XOGA0D TYrkU9rT1QJ21PLik7KB/K5nuVXkbpa7FzXWgty0325tVJd77XBYhJ4U8dT6H2y+jzHZ6m MJAHPxNYDBVzZwkkdfLZQ2eqk7SqfG+oaeMMqRPAdxNfxLomaoE5RIuJt9RJ3g== Date: Fri, 13 Sep 2024 18:24:38 +0200 From: Erik Wienhold To: Sathish Reddy Cc: pgsql-admin@lists.postgresql.org, Keith Fiske , Crunchy Bridge Support Subject: Re: Pg dump of parent table instead of taking child table Message-ID: <4996c1e7-2eec-4fae-ad75-b337cfad65de@ewie.name> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Rspamd-Queue-Id: 4X505520vxz9sWx List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-09-13 15:11 +0200, Sathish Reddy wrote: > We are using 14 version > Pg_dump with -Fp and --loading-via-parent-root option > > > > Database name is better and schema is better. .. But how are the tables defined, i.e., the CREATE TABLE statements? Are we talking about table partitions when you're possibly using --load-via-partition-root (as noted downthread)? > On Fri, Sep 13, 2024, 6:24 PM Erik Wienhold wrote: > > > On 2024-09-13 13:30 +0200, Sathish Reddy wrote: > > > We are trying to take parent table backup included all child tables data > > > into dump plan format.but we are getting failed to achieve. > > > > 1) Which Postgres version? > > > > 2) What pg_dump options did you use? > > > > 3) What output/error do you get? > > > > 4) What does the database schema look like? Are you using table > > inheritance or foreign keys for the parent-child relationship? -- Erik