Re: pg_dump of partitioned table not working.

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: "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:36:00
Message-ID: f57cc88f-50bb-e5bb-5f9d-8a25b2008eb9@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/2/20 6:21 PM, David G. Johnston wrote:
> On Wed, Dec 2, 2020 at 5:14 PM Ron <ronljohnsonjr(at)gmail(dot)com
> <mailto: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).

That's doable, but the developer (of the very large mission-critical
*existing application*) would probably push back.

--
Angular momentum makes the world go 'round.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2020-12-03 00:38:14 Re: pg_dump of partitioned table not working.
Previous Message David G. Johnston 2020-12-03 00:21:34 Re: pg_dump of partitioned table not working.