aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2021-04-23 15:45:46 +0900
committerFujii Masao <fujii@postgresql.org>2021-04-23 15:48:06 +0900
commitd59964999d15be29fcd97544e66780fc5c9f17a9 (patch)
tree70ecc84d64bf9b41f6e34263c9e9d50ad417a50b /src/backend/executor/nodeModifyTable.c
parent246e9f0341ef6215c09f398ea90ae09abdf5d714 (diff)
downloadpostgresql-d59964999d15be29fcd97544e66780fc5c9f17a9.tar.gz
postgresql-d59964999d15be29fcd97544e66780fc5c9f17a9.zip
doc: Fix obsolete description about pg_basebackup.
Previously it was documented that if using "-X none" option there was no guarantee that all required WAL files were archived at the end of pg_basebackup when taking a backup from the standby. But this limitation was removed by commit 52f8a59dd9. Now, even when taking a backup from the standby, pg_basebackup can wait for all required WAL files to be archived. Therefore this commit removes such obsolete description from the docs. Also this commit adds new description about the limitation when taking a backup from the standby, into the docs. The limitation is that pg_basebackup cannot force the standbfy to switch to a new WAL file at the end of backup, which may cause pg_basebackup to wait a long time for the last required WAL file to be switched and archived, especially when write activity on the primary is low. Back-patch to v10 where the issue was introduced. Reported-by: Kyotaro Horiguchi Author: Kyotaro Horiguchi, Fujii Masao Reviewed-by: Kyotaro Horiguchi, Fujii Masao Discussion: https://postgr.es/m/20210420.133235.1342729068750553399.horikyota.ntt@gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions