Re: pg_dump of partitioned table not working.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump of partitioned table not working.
Date: 2020-12-03 00:21:34
Message-ID: CAKFQuwY5dkPtx9Q67dJfVTJuf+=E5TfGTbpQ2ej76OBm0gnCLg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 2, 2020 at 5:14 PM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:

>
> > It does seem like there might be reason to have a switch along
> > the lines of "--include-child-tables".
>
> That would be great, but won't help me in v12.
>
>
I'd probably just relocate the table to a separate schema and require that
all partitions are placed there as well. Otherwise, the necessary
information exists in the catalogs, so a solution is within reach (minor
concern regarding concurrency).

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2020-12-03 00:36:00 Re: pg_dump of partitioned table not working.
Previous Message Adrian Klaver 2020-12-03 00:21:10 Re: pg_dump of partitioned table not working.