summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-03-17 15:05:17 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-03-17 15:05:17 -0400
commit9a9b87191a32fb97dbd9cad6d9a8a43a9fc31c16 (patch)
tree3af6c08aba94e8a663cf2a4c354a40f520ae7443 /src/backend/access/gist/gistbuildbuffers.c
parentcd6a0518794d939ed6a716c1a13ead2900b11d50 (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.
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions