| From: | Alexander Korotkov <akorotkov(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Document that WAIT FOR may be interrupted by recovery conflicts |
| Date: | 2026-04-06 19:47:42 |
| Message-ID: | E1w9pvB-003HW4-1H@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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(at)gmail(dot)com>
Reviewed-by: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/10484c2cc75be3746933d2052b18e8c28512f69e
Modified Files
--------------
doc/src/sgml/ref/wait_for.sgml | 10 ++++++++++
1 file changed, 10 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-04-06 19:56:52 | pgsql: Add CONCURRENTLY option to REPACK |
| Previous Message | Nathan Bossart | 2026-04-06 19:31:32 | pgsql: Remove recheck_relation_needs_vacanalyze(). |