On Tue, May 6, 2025 at 10:13:36PM +0800, jian he wrote:
> Add pg_dump options --with-schema, --with-data, and --with_statistics
> (Jeff Davis) §
> The negative versions of these options already existed.
>
> Add pg_dump option --sequence-data to dump sequence data that would
> normally be excluded (Nathan Bossart) §
>
> Add pg_dump, pg_dumpall, and pg_restore options --statistics-only,
> --no-statistics, --no-data, and --no-schema (Corey Huinker, Jeff
> Davis) §
> ````
>
> in pg17, we only have "--schema-only", "--data-only",
> so description "The negative versions of these options already
> existed." is wrong?
> you can also see the above third item conflict with it.
>
> ``--with_statistics`` should be ``--with-statistics``.
>
>
>
> Add option --no-policies to pg_dump, pg_dumpall, pg_restore to avoid
> policy specification (Nikolay Samokhvalov) §
> This is useful for migrating to systems with different policies.
>
> generally, we should say "row level security policy" instead of "policy"?
> I think this sentence ( Add --no-policies option to control row level
> security policy handling
> in dump and restore operations.) in the commit message is good.
> maybe we can change it to
> ( Add --no-policies option to control row level security policy
> handling in pg_dump, pg_dumpall, pg_restore)
>
>
>
> Allow jsonb NULL values to be cast to scalar types as NULL (Tom Lane) §
> Previously such casts generated an error.
>
> here should be "jsonb null values", since we can not do ``select
> 'NULL'::jsonb;``
All fixed in the attached applied patch.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
