Re: WAL on a RAM disk

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: David Parker <dparker(at)tazznetworks(dot)com>
Cc: postgres general <pgsql-general(at)postgresql(dot)org>
Subject: Re: WAL on a RAM disk
Date: 2005-04-07 14:52:50
Message-ID: 42554942.30200@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Parker wrote:

> 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?

No.

> If not, what configuration of WAL/Checkpoint settings would result in
> minimal WAL activity?

You could turn off fsync.

>
> 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?)

Low.

>
> 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.

You could get a small solid state disk and put your wal on that.

Sincerely,

Joshua D. Drake

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

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL

Attachment Content-Type Size
jd.vcf text/x-vcard 285 bytes

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2005-04-07 15:00:00 Re: WAL on a RAM disk
Previous Message David Parker 2005-04-07 14:38:58 WAL on a RAM disk