projects / postgresql.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: da25414) | patch
Doc: clarify behavior of "anyrange" pseudo-type.
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 17 Mar 2020 19:05:17 +0000 (15:05 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 17 Mar 2020 19:05:17 +0000 (15:05 -0400)
commitf99363e23102c1dceb83d066e3b16c4688079634
treed07f8b3c5fe8c38baa7d02cb14b0c20b70e2d538tree
parentda254148f4deff3cc5f4a5003e5b3c026c04f4a9commit | 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.