From 4a9b44d3c075fe73661d0407faf6f048075a00f9 Mon Sep 17 00:00:00 2001
From: Andrew Gierth <rhodiumtoad@postgresql.org>
Date: Thu, 17 May 2018 21:19:57 +0100
Subject: [PATCH] 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.
---
 doc/src/sgml/func.sgml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

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>