Re: PG 18 release notes draft committed

On Fri, May 2, 2025 at 10:44 AM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> release-16: 206
> release-17: 182
> release-18: 209
>
> I will continue improving it until beta 1, and until the final release.
> I will probably add markup in 1-3 weeks. Let the feedback begin. ;-)
>
> You can see the most current HTML-built version here:
>
> https://momjian.us/pgsql_docs/release-18.html
>

```
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;``