Re: PG 14 release notes, first draft

[Bruce Momjian]

On Mon, Jun 28, 2021 at 09:25:47PM -0500, Justin Pryzby wrote:
> On Mon, Jun 28, 2021 at 09:01:40PM -0400, Bruce Momjian wrote:
> > so we are talking about scans in parallel, so I think it is plural.  Wrong?
> 
> I think the "type" of scan being referenced is a "parallel" type, right ?
> So there's only one type, but multiple scans.
> So I think it should say "this type" of scan, but it seems like it's not only
> easier but generally better to say
> 
> | postgres_fdw supports parallel scans if async_capable
> 
> >> 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-strict comparisons, 
> >> leading to confusion. The old operators still exist but will be eventually 
> >> removed.
> 
> > What markup is missing?
> 
> I mean markup for the operators, like <literal>&lt;@</literal>
> 
> > Uh, why?  I don't see the release notes as a place to explain how to use
> > Postgres features.
> 
> Because the normal way to show foreign keys (\d) doesn't show them - the
> references are shown by the function.

OK, agreed.  Here is an updated applied patch.

-- 
  Bruce Momjian  <br...@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  If only the physical world exists, free will is an illusion.


diff --git a/doc/src/sgml/release-14.sgml b/doc/src/sgml/release-14.sgml
index e96206f899..03ee36867a 100644
--- a/doc/src/sgml/release-14.sgml
+++ b/doc/src/sgml/release-14.sgml
@@ -58,8 +58,9 @@ Author: Tom Lane <t...@sss.pgh.pa.us>
 -->
 
      <para>
-      Prevent the containment operators (&lt;@ and @&gt;) for <xref
-      linkend="intarray"/> from using GiST indexes (Tom Lane)
+      Prevent the containment operators (<literal>&lt;@</literal> and
+      <literal>@&gt;</literal>) for <xref linkend="intarray"/> from using
+      GiST indexes (Tom Lane)
      </para>
 
      <para>
@@ -78,8 +79,9 @@ Author: Tom Lane <t...@sss.pgh.pa.us>
 -->
 
      <para>
-      Remove deprecated containment operators @ and ~ for built-in
-      <link linkend="functions-geometry">geometric data types</link> and
+      Remove deprecated containment operators <literal>@</literal>
+      and <literal>~</literal> for built-in <link
+      linkend="functions-geometry">geometric data types</link> and
       contrib modules <xref linkend="cube"/>, <xref linkend="hstore"/>,
       <xref linkend="intarray"/>, and <xref linkend="seg"/> (Justin Pryzby)
      </para>
@@ -1216,7 +1218,7 @@ Author: Etsuro Fujita <efuj...@postgresql.org>
        <para>
         <link
         linkend="postgres-fdw"><application>postgres_fdw</application></link>
-        supports these type of scans if <literal>async_capable</literal>
+        supports this type of scan if <literal>async_capable</literal>
         is set.
        </para>
       </listitem>
@@ -2398,7 +2400,9 @@ Author: Tom Lane <t...@sss.pgh.pa.us>
       </para>
 
       <para>
-       This helps <acronym>GUI</acronym> tools analyze the system tables.
+       This helps <acronym>GUI</acronym> tools analyze the
+       system tables.  The constraints are visible using <link
+       linkend="functions-aclitem-fn-table">pg_get_catalog_foreign_keys()</link>.
       </para>
      </listitem>
 
@@ -2495,15 +2499,16 @@ Author: Tom Lane <t...@sss.pgh.pa.us>
 
       <para>
        Add <link linkend="functions-geometry">point operators</link>
-       &lt;&lt;| and |&gt;&gt; to be strictly above/below geometry
-       (Emre Hasegeli)
+       <literal>&lt;&lt;|</literal> and <literal>|&gt;&gt;</literal>
+       to be strictly above/below geometry (Emre Hasegeli)
       </para>
 
       <para>
-       Previously &gt;^ and &lt;^ were marked as performing this test, but
-       non-point geometric operators used these operators for non-strict
-       comparisons, leading to confusion.  The old operators still exist
-       but will be eventually removed.  ACCURATE?
+       Previously <literal>&gt;^</literal> and <literal>&lt;^</literal>
+       were marked as performing this test, but non-point geometric
+       operators used these operators for non-strict comparisons, leading
+       to confusion.  The old operators still exist but will be eventually
+       removed.  ACCURATE?
       </para>
      </listitem>