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

Re: Disable WAL completely

From: Erik Jones <erik(at)myemma(dot)com>
To: depesz(at)depesz(dot)com
Cc: "Kathirvel, Jeevanandam" <Jeevanandam(dot)Kathirvel(at)honeywell(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Disable WAL completely
Date: 2008-02-18 15:34:44
Message-ID: 3C31118E-D5EB-4F3A-ACB8-50F17F195EA5@myemma.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Feb 18, 2008, at 3:32 AM, hubert depesz lubaczewski wrote:

> On Mon, Feb 18, 2008 at 03:00:47PM +0530, Kathirvel, Jeevanandam  
> wrote:
>> 	Is there way to minimize the I/O operation on disk/CF.
>> 	Can I create RAM file system and point the pg_xlog files to RAM
>> location instead of CF.  whether this will work?
>
> it will, but in case you'll lost power you will also (most probably)
> loose your database.

Right.  Without the xlog directory you'll have very little chance of  
ever doing any kind of clean stop/start of your database.  If you  
don't need the reliability offered by Postgres's use of transaction  
logs you'll probably be much better served with a different database  
or even a completely different storage scheme than trying to make  
Postgres fit that bill.

Erik Jones

DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com




In response to

Responses

pgsql-performance by date

Next:From: Albert Cervera ArenyDate: 2008-02-18 15:50:41
Subject: Re: Controling where temporary files are created
Previous:From: Nikolas EverettDate: 2008-02-18 15:27:39
Subject: Controling where temporary files are created

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