aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2022-07-12 11:53:29 +0900
committerFujii Masao <fujii@postgresql.org>2022-07-20 09:57:07 +0900
commit0829cc43ed69252184f90161b4940444d8b48574 (patch)
tree8dd967ceb2655ad882171d9efa829d1bbc6fba40 /contrib/postgres_fdw/postgres_fdw.c
parent286793b9889f8adaf76025debb7925a56a20b29c (diff)
downloadpostgresql-0829cc43ed69252184f90161b4940444d8b48574.tar.gz
postgresql-0829cc43ed69252184f90161b4940444d8b48574.zip
Fix assertion failure and segmentation fault in backup code.
When a non-exclusive backup is canceled, do_pg_abort_backup() is called and resets some variables set by pg_backup_start (pg_start_backup in v14 or before). But previously it forgot to reset the session state indicating whether a non-exclusive backup is in progress or not in this session. This issue could cause an assertion failure when the session running BASE_BACKUP is terminated after it executed pg_backup_start and pg_backup_stop (pg_stop_backup in v14 or before). Also it could cause a segmentation fault when pg_backup_stop is called after BASE_BACKUP in the same session is canceled. This commit fixes the issue by making do_pg_abort_backup reset that session state. Back-patch to all supported branches. Author: Fujii Masao Reviewed-by: Kyotaro Horiguchi, Masahiko Sawada, Michael Paquier, Robert Haas Discussion: https://postgr.es/m/3374718f-9fbf-a950-6d66-d973e027f44c@oss.nttdata.com
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions