| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <stark(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |
| Date: | 2010-02-22 15:42:08 |
| Message-ID: | 25289.1266853328@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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"
phase?
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-02-22 17:15:10 | pgsql: Briefly document in two places that pg_dump and pg_dumpall cannot |
| Previous Message | Tom Lane | 2010-02-22 15:29:46 | pgsql: Let's try forcing errno to zero before issuing fsync. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-02-22 16:42:37 | Re: Recent vendor SSL renegotiation patches break PostgreSQL |
| Previous Message | Bruce Momjian | 2010-02-22 15:32:17 | Re: ALTER TABLE SET STATISTICS requires AccessExclusiveLock |