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 1sp5on-00GSYV-8J for pgsql-admin@arkaria.postgresql.org; Fri, 13 Sep 2024 12:54:34 +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 1sp5ol-002X3D-Sc for pgsql-admin@arkaria.postgresql.org; Fri, 13 Sep 2024 12:54:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sp5ol-002X35-Eo for pgsql-admin@lists.postgresql.org; Fri, 13 Sep 2024 12:54:31 +0000 Received: from mout-u-107.mailbox.org ([80.241.59.207]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sp5oi-000y06-5u for pgsql-admin@lists.postgresql.org; Fri, 13 Sep 2024 12:54:30 +0000 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (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-107.mailbox.org (Postfix) with ESMTPS id 4X4vQQ3jk6z9sTS; Fri, 13 Sep 2024 14:54:22 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1726232062; 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: in-reply-to:in-reply-to:references:references; bh=2Ry4BDIwR4Kajx/EA3mRk6nhH4S0mMzQg5RUrKiZH6c=; b=Am05L4vSFGMCZGx9qkNQHGo2PJpsrOzSTb2OzOZVn9eBjkd1AbOyPpxLsRuKYkyvmUOKwX IuQBAi2L3Vxx5UvDHlSt6sh78F78aZALFu4iVfLeRLr6XqL9Fl1bul4nO97aob8VJWUWBz HHoW+C5ZXIoBaa26HygdRduReDhNG4ATt0t+eUKNNXIbUeMrRfsxDqdROCscXp718BOzO8 DluV8upAGRSQJbY2fa9W4jAaWcTb/C2QeL6zmrzlGoyjrdfWCo70dmZ7ngODLDqMbW/+nX 0tVM8eWjNmsPvPSCdDTudJqu/snJxocsT1u8bRQ6BzJ6xCMKzjPmQ2l3aUPgpQ== Date: Fri, 13 Sep 2024 14:54:19 +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: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4X4vQQ3jk6z9sTS List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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