From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Simplifying wal_sync_method |
Date: | 2005-08-09 05:28:33 |
Message-ID: | 200508090528.j795SXd17259@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > My proposal is to remove fdatasync and open_datasync, and have have
> > fsync _prefer_ fdatasync, and open_sync prefer open_datastync, but fall
> > back to fsync and open_sync if the *data* version are not supported.
>
> And this will buy us what, other than lack of flexibility?
Clarity in testing options.
> The "data" options already are the default when available, I think
> (if not, I have no objection to making them so). That does not
They are.
> equate to saying we should remove access to the other options.
> Your argument that they are useless only holds up in a perfect
> world where there are no hardware bugs and no kernel bugs ...
> and last I checked, we do not live in such a world.
Is it useful to have the option of using non-*data* options when *data*
options are available? I have never heard of anyone wanting to do that,
nor do I imagine anyone doing that. Is there a real use case?
--
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 | Reini Urban | 2005-08-09 06:09:50 | Re: Cygwin - make check broken |
Previous Message | Tom Lane | 2005-08-09 05:24:40 | Re: Simplifying wal_sync_method |