From a22873a19ef62085dbd93ea4fa992c49a2be5e30 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sun, 12 Feb 2006 19:02:28 +0000
Subject: [PATCH] > Actually, if you submit a patch that says either "SCROLL is
the default" > or "NO SCROLL is the default", it will be rejected as
incorrect. The > reason is that the default behavior is different from
either of these, > as is explained in the NOTES section.
Ok, so *that's* where the bit about the query plan being simple enough.
Based on that, ISTM that it should be premissable for us to decide that
a cursor requiring a sort isn't "simple enough" to support SCROLL.
In any case, here's a patch that makes the non-standard behavior easier
for people to find.
Jim C. Nasby
---
doc/src/sgml/ref/declare.sgml | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml
index 0263145927d..fd7a682917d 100644
--- a/doc/src/sgml/ref/declare.sgml
+++ b/doc/src/sgml/ref/declare.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/declare.sgml,v 1.33 2005/01/04 00:39:53 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/declare.sgml,v 1.33.6.1 2006/02/12 19:02:28 momjian Exp $
PostgreSQL documentation
-->
@@ -129,7 +129,9 @@ DECLARE <replaceable class="parameter">name</replaceable> [ BINARY ] [ INSENSITI
execution plan, specifying <literal>SCROLL</literal> may impose
a performance penalty on the query's execution time.
<literal>NO SCROLL</literal> specifies that the cursor cannot be
- used to retrieve rows in a nonsequential fashion.
+ used to retrieve rows in a nonsequential fashion. The default is to
+ allow scrolling, but this is not the same as specifying
+ <literal>SCROLL</literal>. See <xref linkend="notes"> for more details.
</para>
</listitem>
</varlistentry>
@@ -198,7 +200,7 @@ DECLARE <replaceable class="parameter">name</replaceable> [ BINARY ] [ INSENSITI
</para>
</refsect1>
- <refsect1>
+ <refsect1 id="notes">
<title>Notes</title>
<para>