diff options
| author | Michael Paquier <michael@paquier.xyz> | 2018-09-02 12:40:30 -0700 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2018-09-02 12:40:30 -0700 |
| commit | caa0c6ceba1fd6ec7b027532d68cecf5dfbbb2db (patch) | |
| tree | 470b0d0839a8cef73feed34f2f02d36e0608029d /src/backend/utils/adt/ruleutils.c | |
| parent | 4299c32316addaad2255e6363b26ba1eec5c3999 (diff) | |
| download | postgresql-caa0c6ceba1fd6ec7b027532d68cecf5dfbbb2db.tar.gz postgresql-caa0c6ceba1fd6ec7b027532d68cecf5dfbbb2db.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/adt/ruleutils.c')
0 files changed, 0 insertions, 0 deletions