From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alex Satrapa <alex(at)lintelsys(dot)com(dot)au>, Jason Tesser <JTesser(at)nbbc(dot)edu>, "Pgsql (E-mail)" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: disaster recovery |
Date: | 2003-11-27 13:35:25 |
Message-ID: | 873cca7x42.fsf@asmodeus.mcnaught.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Doug McNaught <doug(at)mcnaught(dot)org> writes:
>> Alex Satrapa <alex(at)lintelsys(dot)com(dot)au> writes:
>>> 1) Under Linux, if you have the file system containing the WAL mounted
>>> with asynchronous writes, "all bets are off".
>> ...
>> Even with ext2, WAL files are preallocated and PG calls fsync() after
>> writing, so in practice it's not likely to cause problems.
>
> Um. I took the reference to "mounted with async write" to mean a
> soft-mounted NFS filesystem. It does not matter which OS you think is
> the one true OS --- running a database over NFS is the act of someone
> with a death wish. But, yeah, soft-mounted NFS is a particularly
> malevolent variety ...
I took it as a garbled understanding of the "Linux does async metadata
updates" criticism. Which is true for ext2, but was never the
show-stopper some BSD-ers wanted it to be. :)
-Doug
From | Date | Subject | |
---|---|---|---|
Next Message | Horák Daniel | 2003-11-27 13:53:34 | Re: Open source data modeling tools for PostgreSQL |
Previous Message | Jonathan Bartlett | 2003-11-27 13:34:22 | Re: What is WAL used for? |