Re: pg_dump --with-* options - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: pg_dump --with-* options
Date
Msg-id 959aacf5c6b102e1541205dc7a30f688d2ddbaec.camel@j-davis.com
Whole thread Raw
In response to Re: pg_dump --with-* options  (Corey Huinker <corey.huinker@gmail.com>)
Responses Re: pg_dump --with-* options
List pgsql-hackers
On Thu, 2025-07-31 at 16:28 -0400, Corey Huinker wrote:
>
> In general, I like the idea of --include, but it would need to be
> consistent in behavior across pg_dump/pg_restore/pg_upgrade(if
> applicable).

How should you exclude stats when doing pg_restore? Presumably, --
include=data,schema. But it's a bit strange if "--include" is the only
way to exclude something.

There are enough nuances and details here that I think the next step is
for someone to turn the idea for --include into a reviewable patch, so
that we can compare it to what we have now and see if people generally
think it's an improvement over what we have now.

Otherwise, we should just proceed with:

https://www.postgresql.org/message-id/40cedfc22da152928a74d472708aaadb8855d8d9.camel@j-davis.com

and close the open item.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: pg_dump --with-* options
Next
From: Arseniy Mukhin
Date:
Subject: Re: amcheck support for BRIN indexes