pgsql: Use a fd opened for read/write when syncing slots during startup

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Use a fd opened for read/write when syncing slots during startup
Date: 2019-10-04 20:44:24
Message-ID: E1iGUR6-0000wQ-0c@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use a fd opened for read/write when syncing slots during startup, take 2.

Cribbing from dfbaed45975:
Some operating systems, including the reporter's windows, return EBADFD
or similar when fsync() is invoked on a O_RDONLY file descriptor.
Unfortunately RestoreSlotFromDisk() does exactly that; which causes
failures after restarts in at least some scenarios.

If you hit the bug the error message will be something like
ERROR: could not fsync file "pg_replslot/$name/state": Bad file descriptor

Simply use O_RDWR instead of O_RDONLY when opening the relevant file
descriptor to fix the bug.

Unfortunately this fix was undone in 82a5649fb9db. Re-apply, and add a
comment.

Bug: 16039
Reported-By: Hans Buschmann
Author: Andres Freund
Discussion: https://postgr.es/m/16039-196fc97cc05e141c@postgresql.org
Backpatch: 12-, as 82a5649fb9db

Branch
------
REL_12_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c025165da9da469ff0136a3eda0070c2b7b6f97e

Modified Files
--------------
src/backend/replication/slot.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2019-10-04 21:36:58 pgsql: Fix crash caused by EPQ happening with a before update trigger p
Previous Message Andres Freund 2019-10-04 20:44:21 pgsql: Use a fd opened for read/write when syncing slots during startup