From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Marko Kreen <marko(at)l-t(dot)ee>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Simplifying wal_sync_method |
Date: | 2005-08-09 03:07:53 |
Message-ID: | 200508090307.j7937rI23371@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Joshua D. Drake wrote:
>
> >>>I think we should offer the reliable option by default, and mention the
> >>>fast option for those who have battery-backed cache in the manual.
> >>
> >>But only on Win32?
> >
> >
> > Yes, because that's the only place where that option works, right?
>
> fsync_writethrough only works on Win32 the postgresql.conf should
> reflect that.
Right now what wal_sync_method supports isn't clear at all. If you have
fdatasync or O_DSYNC (and it has a different value from O_SYNC/O_FSYNC),
you have those, if not, you get an error. For example, my system
doesn't have fdatasync(), so if I try to use that value I get this in my
server logs:
FATAL: invalid value for parameter "wal_sync_method": "fdatasync"
and the server does not start. Also, writethrough is supported in 8.1
by both Win32 and OS X.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Brendan Jurd | 2005-08-09 03:16:26 | Re: Back from OSCON |
Previous Message | Tom Lane | 2005-08-09 02:51:27 | Re: prevent encoding conversion recursive error |