diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-03-17 15:05:17 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-03-17 15:05:17 -0400 |
| commit | f99363e23102c1dceb83d066e3b16c4688079634 (patch) | |
| tree | d07f8b3c5fe8c38baa7d02cb14b0c20b70e2d538 /src/backend/access/gist | |
| parent | da254148f4deff3cc5f4a5003e5b3c026c04f4a9 (diff) | |
| download | postgresql-f99363e23102c1dceb83d066e3b16c4688079634.tar.gz postgresql-f99363e23102c1dceb83d066e3b16c4688079634.zip | |
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.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions