pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Pierre C <lists@peufeu.com>
To: Tadipathri Raghu <traghu.dba@gmail.com>
Cc: Jaime Casanova <jcasanov@systemguards.com.ec>
Cc: pgsql-performance@postgresql.org
Subject: Re: Why Wal_buffer is 64KB
Date: Fri, 26 Mar 2010 14:43:45 +0100
Message-ID: <op.u96ge7lfeorkce@localhost> (raw)
In-Reply-To: <645d9d71003252019u6f01a513x7876c1a97b448dea@mail.gmail.com>
References: <645d9d71003250801o246439a0j93c7b568786e98de@mail.gmail.com>
	<3073cc9b1003251015x590e962ata59dadbb58b42ce5@mail.gmail.com>
	<op.u94yaoixeorkce@localhost>
	<645d9d71003252019u6f01a513x7876c1a97b448dea@mail.gmail.com>


> After fsync/syncronous_commit off

Do not use fsync off, it is not safe. Who cares about the performance of  
fsync=off, when in practice you'd never use it with real data.
synchronnous_commit=off is fine for some applications, though.

More info is needed about your configuration (hardware, drives, memory,  
etc).

view thread (11+ messages)  latest in thread

Message-ID: <op.u96ge7lfeorkce@localhost>
Permalink:  ../op.u96ge7lfeorkce@localhost/
Also on:    postgresql.org/message-id/op.u96ge7lfeorkce@localhost

copy link · copy postgr.es

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: lists@peufeu.com, traghu.dba@gmail.com, jcasanov@systemguards.com.ec
  Subject: Re: Why Wal_buffer is 64KB
  In-Reply-To: <op.u96ge7lfeorkce@localhost>

* 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