From: Steve Wampler <swampler@noao.edu>
To: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL as a local in-memory cache
Date: Tue, 15 Jun 2010 09:02:31 -0700
Message-ID: <4C17A417.2040600@noao.edu> (raw)
In-Reply-To: <87bpbcpabg.fsf@cbbrowne-laptop.afilias-int.info>
References: <cb0fb58c-9134-4314-a1d0-08fc39f911a6@40g2000pry.googlegroups.com>
<87bpbcpabg.fsf@cbbrowne-laptop.afilias-int.info>
Chris Browne wrote:
> "jgardner@jonathangardner.net" <jgardner@jonathangardner.net> writes:
>> My question is how can I configure the database to run as quickly as
>> possible if I don't care about data consistency or durability? That
>> is, the data is updated so often and it can be reproduced fairly
>> rapidly so that if there is a server crash or random particles from
>> space mess up memory we'd just restart the machine and move on.
>
> For such a scenario, I'd suggest you:
>
> - Set up a filesystem that is memory-backed. On Linux, RamFS or TmpFS
> are reasonable options for this.
>
> - The complication would be that your "restart the machine and move
> on" needs to consist of quite a few steps:
>
> - recreating the filesystem
> - fixing permissions as needed
> - running initdb to set up new PG instance
> - automating any needful fiddling with postgresql.conf, pg_hba.conf
> - starting up that PG instance
> - creating users, databases, schemas, ...
Doesn't PG now support putting both WAL and user table files onto
file systems other than the one holding the PG config files and PG
'admin' tables? Wouldn't doing so simplify the above considertably
by allowing just the WAL and user tables on the memory-backed file
systems? I wouldn't think the performance impact of leaving
the rest of the stuff on disk would be that large.
Or does losing WAL files mandate a new initdb?
--
Steve Wampler -- swampler@noao.edu
The gods that smiled on your birth are now laughing out loud.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: swampler@noao.edu
Subject: Re: PostgreSQL as a local in-memory cache
In-Reply-To: <4C17A417.2040600@noao.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox