Skip site navigation (1) Skip section navigation (2)

Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marti Raudsepp <marti(at)juffo(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+
Date: 2010-11-05 18:13:47
Message-ID: 27641.1288980827@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Marti Raudsepp <marti(at)juffo(dot)org> writes:
> PostgreSQL's default settings change when built with Linux kernel
> headers 2.6.33 or newer. As discussed on the pgsql-performance list,
> this causes a significant performance regression:
> http://archives.postgresql.org/pgsql-performance/2010-10/msg00602.php

> NB! I am not proposing to change the default -- to the contrary --
> this patch restores old behavior.

I'm less than convinced this is the right approach ...

If open_dsync is so bad for performance on Linux, maybe it's bad
everywhere?  Should we be rethinking the default preference order?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2010-11-05 18:14:43
Subject: Re: ALTER OBJECT any_name SET SCHEMA name
Previous:From: Tom LaneDate: 2010-11-05 18:04:15
Subject: Re: ALTER TABLE ... IF EXISTS feature?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group