aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorFujii Masao <fujii@postgresql.org>2015-09-09 22:51:44 +0900
committerFujii Masao <fujii@postgresql.org>2015-09-09 23:03:17 +0900
commit60fe73b79ce8a65ee4eda34a2f4f204a95081603 (patch)
tree504840345b8168a9635a63f980b7db92d1657ee4 /src/backend/executor/nodeModifyTable.c
parentda5fb2af3520acbc5230a77549cfd1a1c874bfb9 (diff)
downloadpostgresql-60fe73b79ce8a65ee4eda34a2f4f204a95081603.tar.gz
postgresql-60fe73b79ce8a65ee4eda34a2f4f204a95081603.zip
Remove files signaling a standby promotion request at postmaster startup
This commit makes postmaster forcibly remove the files signaling a standby promotion request. Otherwise, the existence of those files can trigger a promotion too early, whether a user wants that or not. This removal of files is usually unnecessary because they can exist only during a few moments during a standby promotion. However there is a race condition: if pg_ctl promote is executed and creates the files during a promotion, the files can stay around even after the server is brought up to new master. Then, if new standby starts by using the backup taken from that master, the files can exist at the server startup and should be removed in order to avoid an unexpected promotion. Back-patch to 9.1 where promote signal file was introduced. Problem reported by Feike Steenbergen. Original patch by Michael Paquier, modified by me. Discussion: 20150528100705.4686.91426@wrigleys.postgresql.org
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions