aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2018-09-02 12:40:58 -0700
committerMichael Paquier <michael@paquier.xyz>2018-09-02 12:40:58 -0700
commit02b1b01d8ed4fad10ad4560604dc45b06968f64a (patch)
tree07f68bafb0e9bac4a006372f6314cc56cbfd4f2a /src/backend/utils
parentd368c6c711d03b8bb674274b2b3653985f305248 (diff)
downloadpostgresql-02b1b01d8ed4fad10ad4560604dc45b06968f64a.tar.gz
postgresql-02b1b01d8ed4fad10ad4560604dc45b06968f64a.zip
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/utils')
0 files changed, 0 insertions, 0 deletions