Hello,
When investigating behavior of "DISCARD ALL", I found that order of
steps of equivalent sequence in documentation is not updated with
changes in code.
Please find attached patch to fix documentation.
Best Regards,
Jan Chochol
From 6c3d4e626e993ae0ab2c05e773beea926c687177 Mon Sep 17 00:00:00 2001
From: Jan Chochol <jan.choc...@gooddata.com>
Date: Mon, 27 May 2019 09:26:07 +0200
Subject: [PATCH] Fix order of steps in DISCARD ALL documentation
Since a874fe7b4c890d1fe3455215a83ca777867beadd portals are closed at
beggining of "DISCARD ALL" sequence.
This fix corrects documentation, so documented order corresponds to
order in code.
---
doc/src/sgml/ref/discard.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/src/sgml/ref/discard.sgml b/doc/src/sgml/ref/discard.sgml
index 6b909b7232..2a5a74950b 100644
--- a/doc/src/sgml/ref/discard.sgml
+++ b/doc/src/sgml/ref/discard.sgml
@@ -84,10 +84,10 @@ DISCARD { ALL | PLANS | SEQUENCES | TEMPORARY | TEMP }
Currently, this has the same effect as executing the following sequence
of statements:
<programlisting>
+CLOSE ALL;
SET SESSION AUTHORIZATION DEFAULT;
RESET ALL;
DEALLOCATE ALL;
-CLOSE ALL;
UNLISTEN *;
SELECT pg_advisory_unlock_all();
DISCARD PLANS;
--
2.19.2
