| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump --with-* options |
| Date: | 2025-08-01 20:02:22 |
| Message-ID: | 959aacf5c6b102e1541205dc7a30f688d2ddbaec.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Arseniy Mukhin | 2025-08-01 20:22:13 | Re: amcheck support for BRIN indexes |
| Previous Message | Jeff Davis | 2025-08-01 19:42:16 | Re: pg_dump --with-* options |