WAL on a RAM disk - Mailing list pgsql-general

From David Parker
Subject WAL on a RAM disk
Date
Msg-id 07FDEE0ED7455A48AC42AC2070EDFF7C5CF56A@corpsrv2.tazznetworks.com
Whole thread Raw
Responses Re: WAL on a RAM disk  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: WAL on a RAM disk  (Stephen Frost <sfrost@snowman.net>)
List pgsql-general
As part of our application we are running a postgres server on a RAM disk. All of the data stored in this database is obviously disposable, and we need to optimize access as much as possible. This is on Solaris 9/intel, postgres 7.4.5. Some things I'm wondering about:
 
1) is it possible to turn off WAL entirely? If not, what configuration of WAL/Checkpoint settings would result in minimal WAL activity?
 
2) Given that the whole database is in memory, does it make sense to set random_page_cost to a high value...or, um... a low value? (Does it show that I don't understand this parameter?)
 
3) Any other settings I should be looking at?
 
Thanks. I don't know if anybody else has done this, but I'd be interested to hear about it, if so.

- DAP
----------------------------------------------------------------------------------
David Parker    Tazz Networks    (401) 709-5130
 

 

pgsql-general by date:

Previous
From: David Gagnon
Date:
Subject: Re: Improvement for COPY command .. unless it already exists
Next
From: "Joshua D. Drake"
Date:
Subject: Re: WAL on a RAM disk