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 1sp65w-00GVvy-J4 for pgsql-admin@arkaria.postgresql.org; Fri, 13 Sep 2024 13:12:17 +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 1sp65v-002nhf-Tm for pgsql-admin@arkaria.postgresql.org; Fri, 13 Sep 2024 13:12:15 +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 1sp65v-002nhW-Fw for pgsql-admin@lists.postgresql.org; Fri, 13 Sep 2024 13:12:15 +0000 Received: from mail-ot1-x330.google.com ([2607:f8b0:4864:20::330]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sp65s-000y7S-Jq for pgsql-admin@lists.postgresql.org; Fri, 13 Sep 2024 13:12:14 +0000 Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-7093c94435bso821834a34.0 for ; Fri, 13 Sep 2024 06:12:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726233132; x=1726837932; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JusTcjN5dn6KUQfi+wQuIl41rb53/YVl3aMkKTmxMhA=; b=T8fiQCDjpFxETyXTYGoTGLjsJFwN1VGiswd1/8UZ+ZSUiEQrpXKY7nYIdlIf9UxvJ9 Spic1T7nlkvWo+/qEkFhAlIk7mVE1L4Wqc4vRjEvzQ4SI25ys7WWb12kC9a52TX1dGRO nSB/h669MNUjXFszLXmluvG/uPzhi4xHMmkcjGIu+09FPuPXtT+eZ3NBNT3rrRUkiE8f hAUr6zJw6gHL6enRcbkv0+1bMnTOexgXOuXNVjUCAz58DgFMh4CCBIrnbT558Cc8c7dA p1ZQdRiC+3pA8I9COKj3LZacMcT2uLmELAOjENmn/vk9mb4PJxpXe7/0PsCiA+ecl6cw DiCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726233132; x=1726837932; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JusTcjN5dn6KUQfi+wQuIl41rb53/YVl3aMkKTmxMhA=; b=uCD7m40A6v4KYz4b8op9UYIJ8Xsir+YWWClILhvNXPS262PoENcWxLl0RKoL2k0ewe d8E71LuyfJ5+LcXZ44lhDmz4b1nGxa+7LZBenKp98va2bkklK5bK7XPGfhy5mrXY62K1 k7ASnpVxTP/bnX6aQn6nO15112CLQ+NOiCWnb8GZpG2/0VBupsMS9C2+eairqdoL8yja gadyoqjQs+blZNT7gQos93jGpo4IquP0BccO2NesfcLRQ2B5loOBd8ZoWHZHySA/P0CD Qp0oK8ilSe+yiTiQbqeXXss+VGmDbLW0FziY1gASloSngblyRGVqJAJqx3HHz/aYEubw J7fA== X-Gm-Message-State: AOJu0YxPFQUo0/ZZcDNko/jjYeTcHajGDG+6CEuSIO5LirdUIGFF20DN LxMTh9JLTYXZB8KCgvyvYljZubTMJ983YbMae1hgUtWxNc7NQfqvQgT4DbWE//tRj52I5TpSwJ+ 1/62yzz485xBYnX22uZXE8Qkyb/8= X-Google-Smtp-Source: AGHT+IHEEBBfPSel5NXYoTANU34nrUndXO4Uh4lmIjyW4W8OkKD7bTTXPGeA/dZbx4x7aw4+sRQzGzzrrwInav8A930= X-Received: by 2002:a05:6830:381a:b0:710:f375:a6c9 with SMTP id 46e09a7af769-71109463c45mr6412827a34.7.1726233132062; Fri, 13 Sep 2024 06:12:12 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Sathish Reddy Date: Fri, 13 Sep 2024 18:41:59 +0530 Message-ID: Subject: Re: Pg dump of parent table instead of taking child table To: Erik Wienhold Cc: pgsql-admin@lists.postgresql.org, Keith Fiske , Crunchy Bridge Support Content-Type: multipart/alternative; boundary="000000000000a2dffe0621fff8bf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a2dffe0621fff8bf Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable We are using 14 version Pg_dump with -Fp and --loading-via-parent-root option Database name is better and schema is better. .. Thanks Sathishreddy On Fri, Sep 13, 2024, 6:24=E2=80=AFPM 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 dat= a > > 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 > --000000000000a2dffe0621fff8bf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

We are using 14 version
Pg_dump with=C2=A0 -Fp and --loading-via-parent-root option=C2=A0



Database name is bet= ter and schema is better. ..



<= /p>

Thanks=C2=A0

Sathishreddy=C2=A0


On Fri= , Sep 13, 2024, 6:24=E2=80=AFPM Erik Wienhold <ewie@ewie.name> wrote:=
On 2024-09-13 13:30 +0200, Sathish= Reddy wrote:
> We are trying to take parent table backup included all child tables da= ta
> 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?=C2=A0 Are you using table
=C2=A0 =C2=A0inheritance or foreign keys for the parent-child relationship?=

--
Erik
--000000000000a2dffe0621fff8bf--