]> granicus.if.org Git - postgresql/commitdiff
Fix order of steps in DISCARD ALL documentation
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 11 Jun 2019 16:22:11 +0000 (12:22 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 11 Jun 2019 16:22:11 +0000 (12:22 -0400)
The docs have always been slightly inaccurate, but got particularly so
in a874fe7b4c89, which made DISCARD ALL occur before everything else;
reorder.

Author: Jan Chochol
Discussion: https://postgr.es/m/CAEASf_3TzBbnXm64HpnD5zCZEh8An9jN8ubMR=De-vOXHMHGeA@mail.gmail.com

doc/src/sgml/ref/discard.sgml

index 6b909b7232aa78b98dc06f7e29a6d8d2dd7d2fcb..bf44c523cac62e94add43451aa9ff7936aacd06a 100644 (file)
@@ -84,15 +84,15 @@ 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;
-DISCARD SEQUENCES;
 DISCARD TEMP;
+DISCARD SEQUENCES;
 </programlisting></para>
     </listitem>
    </varlistentry>