From 000086b49cb7b8f38e9fba76121d7ea894421b9b Mon Sep 17 00:00:00 2001
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Mon, 12 May 2008 16:23:26 +0000
Subject: [PATCH] Document that "ROLLBACK TO savepoint" does not un-close
 cursors.

---
 doc/src/sgml/ref/close.sgml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/close.sgml b/doc/src/sgml/ref/close.sgml
index f4fada4ac71..24a060b0026 100644
--- a/doc/src/sgml/ref/close.sgml
+++ b/doc/src/sgml/ref/close.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/close.sgml,v 1.26 2007/05/15 19:13:55 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/close.sgml,v 1.27 2008/05/12 16:23:26 alvherre Exp $
 PostgreSQL documentation
 -->
 
@@ -91,6 +91,12 @@ CLOSE { <replaceable class="PARAMETER">name</replaceable> | ALL }
    You can see all available cursors by querying the <link
    linkend="view-pg-cursors"><structname>pg_cursors</></> system view.
   </para>
+
+  <para>
+   If a cursor is closed after a savepoint which is later rolled back,
+   the <command>CLOSE</command> is not rolled back; that is, the cursor
+   remains closed.
+  </para>
  </refsect1>
 
  <refsect1>
-- 
2.39.5