BTW, I notice that after allegedly fixing things, we are now seeing
fsync failures during CREATE DATABASE in the installcheck phase of
buildfarm runs on (apparently) all the Windows critters, plus a
couple of other platforms too. This mystifies me. I could believe
that there was something still wrong with copydir.c, but then how
come these machines are getting through the earlier "make check"
I made a couple of code tweaks just now to try to get more information
--- the reported EBADF error numbers seem fairly implausible in
themselves, so I wondered if that's *really* what fsync is reporting.
I don't have a lot of hope for that though.
Any theories about what is happening?
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2010-02-22 16:42:37|
|Subject: Re: Recent vendor SSL renegotiation patches break PostgreSQL|
|Previous:||From: Bruce Momjian||Date: 2010-02-22 15:32:17|
|Subject: Re: ALTER TABLE SET STATISTICS requires
pgsql-committers by date
|Next:||From: Bruce Momjian||Date: 2010-02-22 17:15:10|
|Subject: pgsql: Briefly document in two places that pg_dump and pg_dumpall cannot |
|Previous:||From: Tom Lane||Date: 2010-02-22 15:29:46|
|Subject: pgsql: Let's try forcing errno to zero before issuing fsync.|