| From: | Erik Wienhold <ewie(at)ewie(dot)name> |
|---|---|
| To: | Sathish Reddy <sathishreddy(dot)postgresql(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, Keith Fiske <keith(dot)fiske(at)crunchydata(dot)com>, Crunchy Bridge Support <bridge-support(at)crunchydata(dot)com> |
| Subject: | Re: Pg dump of parent table instead of taking child table |
| Date: | 2024-09-13 16:24:38 |
| Message-ID: | 4996c1e7-2eec-4fae-ad75-b337cfad65de@ewie.name |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 <ewie(at)ewie(dot)name> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wells Oliver | 2024-09-13 16:55:48 | Re: Query plan getting less efficient over time with frequent updates and deletes.. |
| Previous Message | David G. Johnston | 2024-09-13 14:16:00 | Re: Pg dump of parent table instead of taking child table |