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

Re: Disable WAL completely

From: Tobias Brox <tobias(at)nordicbet(dot)com>
To: Erik Jones <erik(at)myemma(dot)com>
Cc: depesz(at)depesz(dot)com,"Kathirvel, Jeevanandam" <Jeevanandam(dot)Kathirvel(at)honeywell(dot)com>,pgsql-performance(at)postgresql(dot)org
Subject: Re: Disable WAL completely
Date: 2008-02-18 16:49:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
[Erik Jones]
> 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.

We actually have some postgres databases that are read-only, others that
can be rebuilt by a script or from some old backup, and yet others that
can be wiped completely without ill effects ... and others where we
would prefer to keep all the data, but it would be no disaster if we
lose some.  Maybe we would be better off not using postgres for those
purposes, but it's oh so much easier for us to stick to one database
system ;-)

We've considered both running postgres from a ram-disk and to have the
fsync turned off for some of our databases, but right now we're running
all off one host, fsync didn't reduce the performance that much, and
after one disasterous power failure we considered that it was not worth
the effort to have fsync turned off.

That being said, postgres is probably not an optimal solution for an
embedded system running on flash memory ;-)

In response to


pgsql-performance by date

Next:From: Chris KratzDate: 2008-02-18 19:32:06
Subject: Re: mis-estimate in nested query causes slow runtimes
Previous:From: Albert Cervera ArenyDate: 2008-02-18 15:50:41
Subject: Re: Controling where temporary files are created

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