diff options
| author | Andrew Gierth <rhodiumtoad@postgresql.org> | 2018-05-17 21:23:01 +0100 |
|---|---|---|
| committer | Andrew Gierth <rhodiumtoad@postgresql.org> | 2018-05-17 21:23:01 +0100 |
| commit | ee68541ce60dd585cbc53142ab9cd14bf10fdf8f (patch) | |
| tree | 795929ffb3cacb05879eeff1ba36ba1794867c3f | |
| parent | aada0a7648e220d6e7a852e827b0d66d04280aed (diff) | |
| download | postgresql-ee68541ce60dd585cbc53142ab9cd14bf10fdf8f.tar.gz postgresql-ee68541ce60dd585cbc53142ab9cd14bf10fdf8f.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 21d22869e84..d9aa7c96072 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -17366,7 +17366,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> |