summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2018-09-02 12:40:52 -0700
committerMichael Paquier <michael@paquier.xyz>2018-09-02 12:40:52 -0700
commitd8030c6842076156c8792cb1613eea1b1422059e (patch)
treefb7e1626126c419e54960f9d7d4ae9299528c451 /src/backend/access/gist/gistproc.c
parent25fb6ba11575515d754477492a5ff83ef0c126c4 (diff)
Fix initial sync of slot parent directory when restoring status
At the beginning of recovery, information from replication slots is recovered from disk to memory. In order to ensure the durability of the information, the status file as well as its parent directory are synced. It happens that the sync on the parent directory was done directly using the status file path, which is logically incorrect, and the current code has been doing a sync on the same object twice in a row. Reported-by: Konstantin Knizhnik Diagnosed-by: Konstantin Knizhnik Author: Michael Paquier Discussion: https://postgr.es/m/9eb1a6d5-b66f-2640-598d-c5ea46b8f68a@postgrespro.ru Backpatch-through: 9.4-
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions