Re: fsync reliability

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fsync reliability
Date: 2011-04-21 13:26:30
Message-ID: 1303392257-sup-9909@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2011-04-21 13:42:22 Re: Formatting Curmudgeons WAS: MMAP Buffers
Previous Message Simon Riggs 2011-04-21 13:01:16 Re: Formatting Curmudgeons WAS: MMAP Buffers