From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pg_stop_backup(wait_for_archive := true) on standby server |
Date: | 2017-06-22 08:12:56 |
Message-ID: | CAD21AoC2Xw6M=ZJyejq_9d_iDkReC_=rpvQRw5QsyzKQdfYpkw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
Since an optional second argument wait_for_archive of pg_stop_backup
has been introduced in PostgreSQL 10 we can choose whether wait for
archiving. But my colleagues found that we can do pg_stop_backup with
wait_for_archive = true on the standby server but it actually doesn't
wait for WAL archiving. Because this behavior is not documented and we
cannot find out it without reading source code it will confuse the
user.
I think we can raise an error when pg_stop_backup with
wait_for_archive = true is executed on the standby. Attached patch
change it so that.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
pg_stop_backup_on_standby.patch | application/octet-stream | 785 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-06-22 08:16:16 | Re: SQL MERGE patches for PostgreSQL Versions |
Previous Message | Kang Yuzhe | 2017-06-22 08:05:03 | SQL MERGE patches for PostgreSQL Versions |