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
fornon-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><@</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 <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
