postgres.git / summary / log / commit / refs

commit    10484c2cc75be3746933d2052b18e8c28512f69e
Author:   Alexander Korotkov <akorotkov@postgresql.org>
Date:     Mon Apr 06 19:42:06 2026 +0000

    Document that WAIT FOR may be interrupted by recovery conflicts
    
    Add a note to the WAIT FOR documentation explaining that sessions
    using this command on a standby server may be interrupted by recovery
    conflicts.  Some conflicts are unavoidable - for example, replaying
    a tablespace drop terminates all backends unconditionally.
    
    Discussion: https://postgr.es/m/CAPpHfds7oSCbZqob7ytT_Lso8fv-NW8LnedUTE4Krde%2B3rkJeA%40mail.gmail.com
    Author: Alexander Korotkov <aekorotkov@gmail.com>
    Reviewed-by: Xuneng Zhou <xunengzhou@gmail.com>


 doc/src/sgml/ref/wait_for.sgml | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/doc/src/sgml/ref/wait_for.sgml b/doc/src/sgml/ref/wait_for.sgml
index df72b3327c8..c30fba6f05a 100644
--- a/doc/src/sgml/ref/wait_for.sgml
+++ b/doc/src/sgml/ref/wait_for.sgml
@@ -253,6 +253,16 @@ WAIT FOR LSN '<replaceable class="parameter">lsn</replaceable>'
    timeline.
   </para>
 
+  <para>
+   On a standby server, <command>WAIT FOR</command> sessions may be
+   interrupted by recovery conflicts.  Some recovery conflicts are
+   unavoidable: for example, replaying a tablespace drop resolves
+   conflicts by terminating all backends, regardless of what they are
+   doing.  Applications using <command>WAIT FOR</command> on a standby
+   should be prepared to handle such interruptions, for example by
+   retrying the command or falling back to an alternative mechanism.
+  </para>
+
 </refsect1>
 
  <refsect1>


[parent: 7e8aeb9e483d]