Re: PG 14 release notes, first draft - Mailing list pgsql-hackers

> Require custom server variable names to use only character which are valid for unquoted SQL identifiers (Tom Lane)

characters plural (since 69a58bfe4)

> This is similar to how Unicode can be specified in literal string.

literal strings

> Add executor method to cache results from the inner-side of nested loop joins (David Rowley)
> This is useful if only a small percentage of rows is checked on the inner side.

I think this should mention the GUC, whether we leave it enabled by default (in
which case people may want to disable it) or disable by default (in which case
people may want to enable it).

> The postgres_fdw supports these type of scans if async_capable is set.
this type
remove "The" ?

> Prevent the containment operators (<@ and @>) for intarray from using GiST indexes (Tom Lane)
> Remove deprecated containment operators @ and ~ for built-in geometric data types and contrib modules cube, hstore,
intarray,and seg (Justin Pryzby)
 
> For example, disregard ^ in its expansion in \1 in (^\d+).*\1.
> Add point operators <<| and |>> to be strictly above/below geometry (Emre Hasegeli)
> Previously >^ and <^ were marked as performing this test, but non-point geometric operators used these operators for
non-strictcomparisons, leading to confusion. The old operators still exist but will be eventually removed. ACCURATE?
 

Should these have markup added?

> Certain discarded tokens, like underscore, caused the output of these functions to produce incorrect tsquery output,
e.g.,both websearch_to_tsquery('"pg_class pg"') and to_tsquery('pg_class <-> pg') used to output '( pg & class ) <->
pg',but now both output 'pg <-> class <-> pg'.
 
> Previously, quoted text that contained multiple adjacent discarded tokens were treated as multiple tokens, causing
incorrecttsquery output, e.g., websearch_to_tsquery('"aaa: bbb"') used to output 'aaa <2> bbb', but now outputs 'aaa
<->bbb'.
 

Missing markup?

> This is controlled by server variable ssl_crl_dir and libpq connection option sslcrldir. Previously only CRL files
couldbe specified.
 
> Allow pgstattuple_approx() to report on TOAST tables (Peter Eisentraut)
> Add pg_stat_statements_info system view to show pg_stat_statements activity (Katsuragi Yuta, Yuki Seino, Naoki
Nakamichi)
> Add postgres_fdw function postgres_fdw_get_connections() to report open foreign server connections (Bharath
Rupireddy)

These should have additional hyperlinks

> Add primary keys, unique constraints, and foreign keys to system catalogs (Peter Eisentraut)

Should mention and link to pg_get_catalog_foreign_keys()

> Pass doubled quote marks in Chapter 36 SQL command strings literally (Tom Lane)

"Chapter 36" looks funny?
See also: 4f7d1c309

>Previously window frame clauses like 'inf' PRECEDING AND 'inf' FOLLOWING returned incorrect results.
>Negative values produced undesirable results.
>Previously such cases returned 1.
>This previously was allowed but produced incorrect results.
>This could be accomplished previously using existing syntax.

All these details could be omitted.

>Only the target table can be referenced.

Could be omitted or folded into the preceding line.

> This was already disabled by default in previous Postgres releases, and most modern OpenSSL and TLS versions no
longersupport it.
 
> This was last used as the default in Postgres 7.3 (year 2002).
> By default, Postgres opens and fsyncs every data file at the start of crash recovery. This new setting,
recovery_init_sync_method=syncfs,instead syncs each filesystem used by the database cluster. This allows for faster
recoveryon systems with many database files.
 
> The new syntax is SUBSTRING(text SIMILAR pattern ESCAPE escapechar). The previous standard syntax was SUBSTRING(text
FROMpattern FOR escapechar), and is still supported by Postgres.
 

These should all say <productname>PostgreSQL</productname>

> Allow psql's \df and \do commands to specify function and operator argument types (Greg Sabino Mullane, Tom Lane)
> Add an access method column to psql's \d[i|m|t]+ output (Georgios Kokolatos)
> Allow psql's \dt and \di to show TOAST tables and their indexes (Justin Pryzby)
> Add psql command \dX to list extended statistics objects (Tatsuro Yamada)
> Fix psql's \dT to understand array syntax and backend grammar aliases, like "int" for "integer" (Greg Sabino Mullane,
TomLane)
 
> When editing the previous query or a file with psql's \e, or using \ef and \ev, ignore the contents if the editor
exitswithout saving (Laurenz Albe)
 

All these slash commands should be <literal>

> Stop pg_upgrade from creating analyze_new_cluster script (Michael Paquier)

It's called analyze_new_cluster.sh (except on window), and it's Magnus' patch.

> EXTRACT(date) now throws an error for units that are not part of the date data type.

"Date data" always seems hard to read.
Could you add markup for "<type>date</type>" ?
Or say: of type "date".

> EXTRACT(date) now throws an error for units that are not part of the date data type.

Could say "if requested to extract units that are not part of the "date" type.

-- 
Justin