pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-performance@postgresql.org, Josh Berkus <josh@agliodbs.com>
Cc: Greg Smith <greg@2ndquadrant.com>
Subject: Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?
Date: Tue, 16 Nov 2010 19:51:28 -0500
Message-ID: <10822.1289955088@sss.pgh.pa.us> (raw)
In-Reply-To: <201011170130.10720.andres@anarazel.de>
References: <AANLkTi=n3zxiLNFhbpiN=JPQPwB=BhXf9iepw1KOEs8U@mail.gmail.com>
	<4CE312D9.6030503@agliodbs.com>
	<9058.1289950294@sss.pgh.pa.us>
	<201011170130.10720.andres@anarazel.de>

Andres Freund <andres@anarazel.de> writes:
> On Wednesday 17 November 2010 00:31:34 Tom Lane wrote:
>> Well, we're not going to increase the default to gigabytes

> Especially not as I don't think it will have any effect after wal_segment_size 
> as that will force a write-out anyway. Or am I misremembering the 
> implementation?

Well, there's a forced fsync after writing the last page of an xlog
file, but I don't believe that proves that more than 16MB of xlog
buffers is useless.  Other processes could still be busy filling the
buffers.

			regards, tom lane



view thread (46+ messages)  latest in thread

Message-ID: <10822.1289955088@sss.pgh.pa.us>
Permalink:  ../10822.1289955088@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/10822.1289955088@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andres@anarazel.de, josh@agliodbs.com, greg@2ndquadrant.com
  Subject: Re: Defaulting wal_sync_method to fdatasync on Linux for 9.1?
  In-Reply-To: <10822.1289955088@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox