aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/connection.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2018-11-22 13:24:57 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2018-11-22 13:25:10 -0500
commitfe375d33a184b98510d08f45f55da1338cde974a (patch)
tree9bed89b8448653c9f17915f11423d0200ea8edc6 /contrib/postgres_fdw/connection.c
parent25c026c284de5ffb1ea5b007afc10158bfab64cb (diff)
downloadpostgresql-fe375d33a184b98510d08f45f55da1338cde974a.tar.gz
postgresql-fe375d33a184b98510d08f45f55da1338cde974a.zip
Doc: rework introductory documentation about covering indexes.
Documenting INCLUDE in the section about unique indexes is confusing, as complained of by Emilio Platzer. Furthermore, it entirely failed to explain why you might want to use the feature. The section about index-only scans is really the right place; it already talked about making such things the hard way. Rewrite that text to describe INCLUDE as the normal way to make a covering index. Also, move that section up a couple of places, as it now seems more important than some of the stuff we had before it. It still has to be after expression and partial indexes, since otherwise some of it would involve forward references. Discussion: https://postgr.es/m/154031939560.30897.14677735588262722042@wrigleys.postgresql.org
Diffstat (limited to 'contrib/postgres_fdw/connection.c')
0 files changed, 0 insertions, 0 deletions