Re: PostgreSQL as a local in-memory cache - Mailing list pgsql-performance

From Tom Lane
Subject Re: PostgreSQL as a local in-memory cache
Date
Msg-id 27712.1277325786@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL as a local in-memory cache  (Dave Page)
Responses Re: PostgreSQL as a local in-memory cache  (Bruce Momjian)
Re: PostgreSQL as a local in-memory cache  (Dimitri Fontaine)
List pgsql-performance
Dave Page <> writes:
> On Wed, Jun 23, 2010 at 9:25 PM, Robert Haas <> wrote:
>> I don't think we need a system-wide setting for that. �I believe that
>> the unlogged tables I'm working on will handle that case.

> Aren't they going to be truncated at startup? If the entire system is
> running without WAL, we would only need to do that in case of an
> unclean shutdown wouldn't we?

The problem with a system-wide no-WAL setting is it means you can't
trust the system catalogs after a crash.  Which means you are forced to
use initdb to recover from any crash, in return for not a lot of savings
(for typical usages where there's not really much churn in the
catalogs).  I tend to agree with Robert that a way to not log content
updates for individual user tables is likely to be much more useful in
practice.

            regards, tom lane

pgsql-performance by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL as a local in-memory cache
Next
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL as a local in-memory cache