| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Dan Scales <scales(at)vmware(dot)com> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: possible new option for wal_sync_method |
| Date: | 2012-02-16 19:49:43 |
| Message-ID: | CABRT9RChp+51kn_Sm_vTtbmLgSfRHVp49GOYJYTgQoXc8zcCoA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 16, 2012 at 19:18, Dan Scales <scales(at)vmware(dot)com> wrote:
> fsync/fdatasync can be very slow on ext3, because it seems to have to
> always wait for the current filesystem meta-data transaction to complete,
> even if that meta-data operation is completely unrelated to the file
> being fsync'ed.
Use the data=writeback mount option to remove this restriction. This
is actually the suggested setting for PostgreSQL file systems:
http://www.postgresql.org/docs/current/static/wal-intro.html
(Note that this is unsafe for some other applications, so I wouldn't
use it on the root file system)
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-02-16 20:06:02 | proposal: copybytea command for psql |
| Previous Message | Tom Lane | 2012-02-16 19:34:34 | Re: Designing an extension for feature-space similarity search |