pgsql: Let's try forcing errno to zero before issuing fsync. - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Let's try forcing errno to zero before issuing fsync.
Date
Msg-id 20100222152946.6627F7541D0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Let's try forcing errno to zero before issuing fsync.  The current buildfarm
results claiming EBADF seem improbable enough that I'm not convinced fsync
is really returning that --- could it be failing to set errno at all?

Modified Files:
--------------
    pgsql/src/port:
        copydir.c (r1.30 -> r1.31)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/port/copydir.c?r1=1.30&r2=1.31)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Adjust pg_fsync_writethrough so that it will set errno when
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Briefly document in two places that pg_dump and pg_dumpall cannot