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>
This commit is contained in:
Alexander Korotkov 2026-04-06 22:42:06 +03:00
parent 7e8aeb9e48
commit 10484c2cc7

View file

@ -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>