RE: Issues with pg_dump command - Mailing list pgsql-bugs

From Lior Dahan
Subject RE: Issues with pg_dump command
Date
Msg-id AM8P192MB110866644C25CE4FFB2278A1BAE10@AM8P192MB1108.EURP192.PROD.OUTLOOK.COM
Whole thread Raw
In response to Re: Issues with pg_dump command  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Issues with pg_dump command
Re: Issues with pg_dump command
List pgsql-bugs
Is there a way we can tell which tables are under this parent one? Perhaps we can dump them instead.

-----Original Message-----
From: Bruce Momjian <bruce@momjian.us> 
Sent: Wednesday, November 18, 2020 4:16 PM
To: Lior Dahan <liord@qmasters.co>
Cc: Daniel Gustafsson <daniel@yesql.se>; pgsql-bugs@postgresql.org; Jonathan Tauman <JonathanT@qmasters.co>
Subject: Re: Issues with pg_dump command

On Wed, Nov 18, 2020 at 01:57:46PM +0000, Lior Dahan wrote:
> We are calling pg_dump for a 9.6.15 PostgreSQL installation (on QRadar).
> 
> Here is the call to the command:
> pg_dump -U qradar -d qradar -a --disable-triggers -t ariel_property
> 
> The dump output looks like this:

Based on the triggers, I wonder if ariel_property is the parent of a partitioned table, and there is nothing in the
parenttable.
 

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee


pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Issues with pg_dump command
Next
From: Bruce Momjian
Date:
Subject: Re: Issues with pg_dump command