| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | pgsql(at)mohawksoft(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: fsync vs open_sync |
| Date: | 2004-08-09 22:34:44 |
| Message-ID: | 200408092234.i79MYi421275@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pgsql(at)mohawksoft(dot)com wrote:
> Furthermore, it seems to also have the added benefit of reducing the I/O
> storm at checkpoints over a system running with fsync off.
>
> I'm really serious about this, changing this one parameter had dramatic
> results on performance. We should have a general call to users to test
> this setting with their OS of choice. If not that, if we can be sure that
> there are no cases where using O_SYNC is worse than fsync() or
> fdatasync(), it should be considered as the default.
Agreed. Have you looked at src/tools/fsync?
--
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 | Gavin Sherry | 2004-08-09 22:42:05 | Re: Tablespace issues (comment on ,moving indexes) |
| Previous Message | Josh Berkus | 2004-08-09 22:30:29 | Postgresql.conf Documentation change |