diff options
| author | Andrew Gierth <rhodiumtoad@postgresql.org> | 2018-05-17 21:19:57 +0100 |
|---|---|---|
| committer | Andrew Gierth <rhodiumtoad@postgresql.org> | 2018-05-17 21:19:57 +0100 |
| commit | 4a9b44d3c075fe73661d0407faf6f048075a00f9 (patch) | |
| tree | b5d792f447e2a7a2557c6296fa7ace4752c54755 | |
| parent | ace3c7cc0518269733c37b37b7aebb9adec2454e (diff) | |
doc: fix description of backward_scan
The description of the index property backward_scan was incorrect and
misleading; rectify.
Backpatch to 9.6 where the amutils functionality was introduced.
| -rw-r--r-- | doc/src/sgml/func.sgml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 29f9e65a88d..89c5d75a3bb 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -16840,7 +16840,9 @@ SELECT pg_type_is_visible('myschema.widget'::regtype); </row> <row> <entry><literal>backward_scan</literal></entry> - <entry>Can the index be scanned backwards? + <entry>Can the scan direction be changed in mid-scan (to + support <literal>FETCH BACKWARD</literal> on a cursor without + needing materialization)? </entry> </row> </tbody> |