| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Allowing WAL fsync to be done via O_SYNC |
| Date: | 2001-03-15 21:39:35 |
| Message-ID: | 200103152139.QAA22787@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> "The default is 'on' if your system defines one of the macros O_SYNC,
> O_DSYNC, O_FSYNC, and if O_SYNC and O_DSYNC are distinct, otherwise the
> default is 'off'."
>
> The net result of this would be that the average user would have
> absolutely no clue what the default on his machine is.
>
> Additionally consider that maybe O_SYNC and O_DSYNC have different values
> but the kernel treats them the same anyway. We really shouldn't try to
> guess that far.
Good point. I think Tom already found dfsync points to fsync in his
libc, or something like that.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2001-03-15 21:40:10 | Re: Allowing WAL fsync to be done via O_SYNC |
| Previous Message | Peter Eisentraut | 2001-03-15 21:37:57 | Re: Allowing WAL fsync to be done via O_SYNC |