pgsql: Let's try forcing errno to zero before issuing fsync.

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Let's try forcing errno to zero before issuing fsync.
Date: 2010-02-22 15:29:46
Message-ID: 20100222152946.6627F7541D0@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-02-22 15:42:08 Re: [COMMITTERS] Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after
Previous Message Tom Lane 2010-02-22 15:26:15 pgsql: Adjust pg_fsync_writethrough so that it will set errno when