Re: fsync reliability - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: fsync reliability
Date
Msg-id 1303392257-sup-9909@alvh.no-ip.org
Whole thread Raw
In response to fsync reliability  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Excerpts from Simon Riggs's message of jue abr 21 05:26:06 -0300 2011:

> ISTM that we can easily do this, since we preallocate WAL files during
> RemoveOldXlogFiles() and rarely extend the number of files.
> So it seems easily possible to fsync the pg_xlog directory at the end
> of RemoveOldXlogFiles(), which is mostly performed by the bgwriter
> anyway.
> 
> It was also noted that "we've always expected the filesystem to take
> care of its own metadata"
> which isn't actually stated anywhere in the docs, AFAIK.
> 
> Perhaps this is an irrelevant problem these days, but would it hurt to fix?

I don't think it's irrelevant (yet).  Even Greg Smith's book suggests to
use ext2 for the WAL partition in extreme cases.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Formatting Curmudgeons WAS: MMAP Buffers
Next
From: "Kevin Grittner"
Date:
Subject: Re: Formatting Curmudgeons WAS: MMAP Buffers