Re: PostgreSQL as a local in-memory cache

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL as a local in-memory cache
Date: 2010-06-15 23:09:58
Message-ID: AANLkTilLIgOiCQbH7MbR19yYlk1-mD7sn7Bvbl8coBBN@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Jun 15, 2010 at 12:37 PM, Chris Browne <cbbrowne(at)acm(dot)org> wrote:
> swampler(at)noao(dot)edu (Steve Wampler) writes:
>> Or does losing WAL files mandate a new initdb?
>
> Losing WAL would mandate initdb, so I'd think this all fits into the
> set of stuff worth putting onto ramfs/tmpfs.  Certainly it'll all be
> significant to the performance focus.

why is that? isn't simply execute pg_resetxlog enough? specially
'cause OP doesn't care about loosing some transactions

--
Jaime Casanova www.2ndQuadrant.com
Soporte y capacitación de PostgreSQL

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2010-06-15 23:18:19 Re: PostgreSQL as a local in-memory cache
Previous Message Yeb Havinga 2010-06-15 19:33:06 Re: B-Heaps