| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marti Raudsepp <marti(at)juffo(dot)org> |
| Subject: | Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ |
| Date: | 2010-11-05 22:08:00 |
| Message-ID: | 201011052308.00616.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday 05 November 2010 22:53:37 Greg Smith wrote:
> > If open_dsync is so bad for performance on Linux, maybe it's bad
> > everywhere? Should we be rethinking the default preference order?
> >
> >
>
> And I've seen the expected sync write performance gain over fdatasync on
> a system with a battery-backed cache running VxFS on Linux, because
> working open_[d]sync means O_DIRECT writes bypassing the OS cache, and
> therefore reducing cache pollution from WAL writes.
Which looks like a setup where you definitely need to know what you do. I.e.
don't need support from wal_sync_method by default being open_fdatasync...
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-11-05 22:10:37 | Re: CREATE CONSTRAINT TRIGGER |
| Previous Message | Tom Lane | 2010-11-05 22:07:10 | Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ |