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

Re: Why Wal_buffer is 64KB

From: "Pierre C" <lists(at)peufeu(dot)com>
To: "Tadipathri Raghu" <traghu(dot)dba(at)gmail(dot)com>
Cc: "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Why Wal_buffer is 64KB
Date: 2010-03-26 13:43:45
Message-ID: op.u96ge7lfeorkce@localhost (view raw or flat)
Thread:
Lists: pgsql-performance
> 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).

In response to

Responses

pgsql-performance by date

Next:From: Scott MarloweDate: 2010-03-26 14:00:38
Subject: Re: Why Wal_buffer is 64KB
Previous:From: Richard HuxtonDate: 2010-03-26 12:18:25
Subject: Re: Performance Tuning Large PL/PGSQL Stored Procedure

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