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

• [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ at 2010-11-05 17:23:35 from Marti Raudsepp

Responses

• Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ at 2010-11-05 19:15:26 from Marti Raudsepp
• Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ at 2010-11-05 20:54:57 from Andres Freund
• Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ at 2010-11-05 21:53:37 from Greg Smith

pgsql-hackers by date

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