aboutsummaryrefslogtreecommitdiff
path: root/src/backend/replication/logical/logicalfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-03-17 15:05:16 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2020-03-17 15:05:16 -0400
commit31d846e0265c2c1415d7910d39d5b259b92184ea (patch)
tree07741516da320922c597195c64386c057e9c2032 /src/backend/replication/logical/logicalfuncs.c
parent9d9784c840f3ac98eb41d021c981eea0fe1735ed (diff)
downloadpostgresql-31d846e0265c2c1415d7910d39d5b259b92184ea.tar.gz
postgresql-31d846e0265c2c1415d7910d39d5b259b92184ea.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/replication/logical/logicalfuncs.c')
0 files changed, 0 insertions, 0 deletions