diff options
| author | Andrew Gierth <rhodiumtoad@postgresql.org> | 2018-05-17 21:23:48 +0100 |
|---|---|---|
| committer | Andrew Gierth <rhodiumtoad@postgresql.org> | 2018-05-17 21:23:48 +0100 |
| commit | 93f6c6328dcf74d1e42162e8f712c23fe16a8cf8 (patch) | |
| tree | 195ccd3085ff874f4d7f208c0db05d46e87dee20 | |
| parent | 91ff29f036349f07b4b48856667735e51ef795a1 (diff) | |
| download | postgresql-93f6c6328dcf74d1e42162e8f712c23fe16a8cf8.tar.gz postgresql-93f6c6328dcf74d1e42162e8f712c23fe16a8cf8.zip | |
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 53a40ddeecf..b851fe023a7 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -17519,7 +17519,9 @@ SELECT currval(pg_get_serial_sequence('sometable', 'id')); </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> |