aboutsummaryrefslogtreecommitdiff
path: root/contrib/btree_gist/btree_numeric.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-02-05 12:55:44 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-02-05 12:55:44 -0500
commitd0cd7b77265cf39e0e8984ba9d5bec0c155dccdb (patch)
tree0ba9b76f922dbe49474724f91857a2894b14bf0e /contrib/btree_gist/btree_numeric.c
parentd13a838e1c19df5358d250b8d469544d7ab3dfda (diff)
downloadpostgresql-d0cd7b77265cf39e0e8984ba9d5bec0c155dccdb.tar.gz
postgresql-d0cd7b77265cf39e0e8984ba9d5bec0c155dccdb.zip
Doc: be clearer that foreign-table partitions need user-added constraints.
A very well-informed user might deduce this from what we said already, but I'd bet against it. Lay it out explicitly. While here, rewrite the comment about tuple routing to be more intelligible to an average SQL user. Per bug #17395 from Alexander Lakhin. Back-patch to v11. (The text in this area is different in v10 and I'm not sufficiently excited about this point to adapt the patch.) Discussion: https://postgr.es/m/17395-8c326292078d1a57@postgresql.org
Diffstat (limited to 'contrib/btree_gist/btree_numeric.c')
0 files changed, 0 insertions, 0 deletions