projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9af2f7d) | patch
Doc: clarify behavior of "anyrange" pseudo-type.
authorTom Lane
Tue, 17 Mar 2020 19:05:17 +0000 (15:05 -0400)
committerTom Lane
Tue, 17 Mar 2020 19:05:17 +0000 (15:05 -0400)
commit974c8ea0afe35a55c1b9ffb9f2090058b9f356dd
tree1cbe2b1aaf88c204e05851e118024d4b4f859efftree
parent9af2f7dc9603bf1fd1f80a6326cc80e83acd3076commit | 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.