projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: d67d724) | patch
Doc: clarify behavior of "anyrange" pseudo-type.
authorTom Lane <[email protected]>
Tue, 17 Mar 2020 19:05:17 +0000 (15:05 -0400)
committerTom Lane <[email protected]>
Tue, 17 Mar 2020 19:05:17 +0000 (15:05 -0400)
commit3c871d1ead20e6744403e2180d704dd09fd8c2d6
tree53b9043a7a4f309a31a3905fb5669948cd0ef2dbtree
parentd67d7243f914f99bd1103f811efd320c987db2bccommit | diff
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.
doc/src/sgml/extend.sgml diff | blob | blame | history
This is the main PostgreSQL git repository.