On Sat, Feb 11, 2006 at 07:50:22PM -0500, Tom Lane wrote:
> > On Sat, 2006-02-11 at 11:44 -0600, Jim C. Nasby wrote:
> >> But speaking of documentation, it doesn't actually say what the default
> >> is. Care update that, or should I formally submit a patch?
> >>
> >> [1] http://www.postgresql.org/docs/8.1/interactive/sql-declare.html
>
> 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, Sr. Engineering Consultant [EMAIL PROTECTED]
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
Index: doc/src/sgml/ref/declare.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v
retrieving revision 1.34
diff -u -r1.34 declare.sgml
--- doc/src/sgml/ref/declare.sgml 18 Jan 2006 06:49:26 -0000 1.34
+++ doc/src/sgml/ref/declare.sgml 12 Feb 2006 05:21:30 -0000
@@ -129,7 +129,9 @@
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 @@
</para>
</refsect1>
- <refsect1>
+ <refsect1 id="notes">
<title>Notes</title>
<para>
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
