| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: initdb and fsync |
| Date: | 2012-02-05 19:50:20 |
| Message-ID: | 18813.1328471420@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Sat, 2012-02-04 at 20:18 -0500, Noah Misch wrote:
>> If we add fsync calls to the initdb process, they should cover the entire data
>> directory tree. This patch syncs files that initdb.c writes, but we ought to
>> also sync files that bootstrap-mode backends had written.
> It doesn't make sense for initdb to take responsibility to sync files
> created by the backend.
No, but the more interesting question is whether bootstrap mode troubles
to fsync its writes. I'm not too sure about that either way ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-02-05 19:56:20 | Re: JSON output functions. |
| Previous Message | Stefan Keller | 2012-02-05 19:31:02 | Re: JSON output functions. |