pgsql: Doc: clarify behavior of "anyrange" pseudo-type.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: clarify behavior of "anyrange" pseudo-type.
Date: 2020-03-17 19:05:36
Message-ID: E1jEHWy-0000hG-ER@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: clarify behavior of "anyrange" pseudo-type.

I noticed that we completely failed to document the restriction
that an "anyrange" result type has to be inferred from an "anyrange"
input. The docs also were less clear than they could be about the
relationship between "anyrange" and "anyarray".

It's been like this all along, so back-patch.

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/bcd460003a722fb421a911309d2f5a7316862084

Modified Files
--------------
doc/src/sgml/extend.sgml | 19 ++++++++++++++++---
1 file changed, 16 insertions(+), 3 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2020-03-17 19:22:17 pgsql: Fix consistency issues with replication slot copy
Previous Message Tom Lane 2020-03-17 18:55:02 pgsql: Remove bogus assertion about polymorphic SQL function result.