From 5e45211a64149b3c659b90ff2de6fa982a5a93ed Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:17:33 +0200 Subject: Adding upstream version 15.5. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/sql-close.html | 42 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 doc/src/sgml/html/sql-close.html (limited to 'doc/src/sgml/html/sql-close.html') diff --git a/doc/src/sgml/html/sql-close.html b/doc/src/sgml/html/sql-close.html new file mode 100644 index 0000000..291862c --- /dev/null +++ b/doc/src/sgml/html/sql-close.html @@ -0,0 +1,42 @@ + +CLOSE

CLOSE

CLOSE — close a cursor

Synopsis

+CLOSE { name | ALL }
+

Description

+ CLOSE frees the resources associated with an open cursor. + After the cursor is closed, no subsequent operations + are allowed on it. A cursor should be closed when it is + no longer needed. +

+ Every non-holdable open cursor is implicitly closed when a + transaction is terminated by COMMIT or + ROLLBACK. A holdable cursor is implicitly + closed if the transaction that created it aborts via + ROLLBACK. If the creating transaction + successfully commits, the holdable cursor remains open until an + explicit CLOSE is executed, or the client + disconnects. +

Parameters

name

+ The name of an open cursor to close. +

ALL

+ Close all open cursors. +

Notes

+ PostgreSQL does not have an explicit + OPEN cursor statement; a cursor is considered + open when it is declared. Use the + DECLARE + statement to declare a cursor. +

+ You can see all available cursors by querying the pg_cursors system view. +

+ If a cursor is closed after a savepoint which is later rolled back, + the CLOSE is not rolled back; that is, the cursor + remains closed. +

Examples

+ Close the cursor liahona: +

+CLOSE liahona;
+

Compatibility

+ CLOSE is fully conforming with the SQL + standard. CLOSE ALL is a PostgreSQL + extension. +

See Also

DECLARE, FETCH, MOVE
\ No newline at end of file -- cgit v1.2.3