Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lz76o-0005Pm-3B for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Jul 2021 00:32:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lz76m-0002DM-Vm for pgsql-hackers@arkaria.postgresql.org; Fri, 02 Jul 2021 00:32:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lz76m-0002DE-O3 for pgsql-hackers@lists.postgresql.org; Fri, 02 Jul 2021 00:32:40 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lz76g-00058I-29 for pgsql-hackers@postgresql.org; Fri, 02 Jul 2021 00:32:40 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1lz76d-00042X-R3; Thu, 01 Jul 2021 20:32:31 -0400 Date: Thu, 1 Jul 2021 20:32:31 -0400 From: Bruce Momjian To: Justin Pryzby Cc: pgsql-hackers@postgresql.org Subject: Re: PG 14 release notes, first draft Message-ID: <20210702003231.GC3618@momjian.us> References: <20210510060308.GC6088@momjian.us> <20210625230456.GP29179@telsasoft.com> <20210629010140.GA32681@momjian.us> <20210629022547.GF21248@telsasoft.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="oC1+HKm2/end4ao3" Content-Disposition: inline In-Reply-To: <20210629022547.GF21248@telsasoft.com> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --oC1+HKm2/end4ao3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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 <@ > > > 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 https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion. --oC1+HKm2/end4ao3 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="REL_14_STABLE.diff" 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 --> - Prevent the containment operators (<@ and @>) for from using GiST indexes (Tom Lane) + Prevent the containment operators (<@ and + @>) for from using + GiST indexes (Tom Lane) @@ -78,8 +79,9 @@ Author: Tom Lane --> - Remove deprecated containment operators @ and ~ for built-in - geometric data types and + Remove deprecated containment operators @ + and ~ for built-in geometric data types and contrib modules , , , and (Justin Pryzby) @@ -1216,7 +1218,7 @@ Author: Etsuro Fujita postgres_fdw - supports these type of scans if async_capable + supports this type of scan if async_capable is set. @@ -2398,7 +2400,9 @@ Author: Tom Lane - This helps GUI tools analyze the system tables. + This helps GUI tools analyze the + system tables. The constraints are visible using pg_get_catalog_foreign_keys(). @@ -2495,15 +2499,16 @@ Author: Tom Lane Add point operators - <<| and |>> to be strictly above/below geometry - (Emre Hasegeli) + <<| 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. ACCURATE? + 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. ACCURATE? --oC1+HKm2/end4ao3--