| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: initdb and fsync |
| Date: | 2012-06-23 09:17:45 |
| Message-ID: | 1340443065.10342.23.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 2012-06-22 at 10:04 -0400, Robert Haas wrote:
> This may be a stupid question, by why is it initdb's job to fsync the
> files the server creates, rather than the server's job? Normally we
> rely on the server to make its own writes persistent.
That was my first reaction as well:
http://archives.postgresql.org/message-id/1328468000.15224.32.camel@jdavis
However, from the discussion it seems like it will be harder to do it
that way (during normal operation, a checkpoint is what syncs the files;
but as Tom points out, bootstrap mode does not). Also, I would expect
the fsyncs to be in a less-controlled pattern, so it might perform more
poorly.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dickson S. Guedes | 2012-06-23 12:21:45 | Re: COMMUTATOR doesn't seem to work |
| Previous Message | Amit Kapila | 2012-06-23 06:53:11 | Re: Allow WAL information to recover corrupted pg_controldata |