WAL on a RAM disk

From: "David Parker" <dparker(at)tazznetworks(dot)com>
To: "postgres general" <pgsql-general(at)postgresql(dot)org>
Subject: WAL on a RAM disk
Date: 2005-04-07 14:38:58
Message-ID: 07FDEE0ED7455A48AC42AC2070EDFF7C5CF56A@corpsrv2.tazznetworks.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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


Responses

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2005-04-07 14:52:50 Re: WAL on a RAM disk
Previous Message David Gagnon 2005-04-07 14:33:13 Re: Improvement for COPY command .. unless it already exists