Re: PostgreSQL as a local in-memory cache

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: PostgreSQL as a local in-memory cache
Date: 2010-06-23 20:16:10
Message-ID: 201006232016.o5NKGAM26947@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Pavel Stehule wrote:
> 2010/6/23 Bruce Momjian <bruce(at)momjian(dot)us>:
> > Tom Lane wrote:
> >> Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
> >> > Josh Berkus <josh(at)agliodbs(dot)com> writes:
> >> >> a) Eliminate WAL logging entirely
> >
> > If we elimiate WAL logging, that means a reinstall is required for even
> > a postmaster crash, which is a new non-durable behavior.
> >
> > Also, we just added wal_level = minimal, which might end up being a poor
> > name choice of we want wal_level = off in PG 9.1. ?Perhaps we should
> > have used wal_level = crash_safe in 9.0.
> >
> > I have added the following TODO:
> >
> > ? ? ? ?Consider a non-crash-safe wal_level that eliminates WAL activity
> >
> > ? ? ? ? ? ?* http://archives.postgresql.org/pgsql-performance/2010-06/msg00300.php
> >
> > --
>
> isn't fsync to off enought?

Well, testing reported in the thread showed other settings also help,
though the checkpoint lengthening was not tested.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ None of us is going to be here forever. +

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Robert Haas 2010-06-23 20:25:44 Re: PostgreSQL as a local in-memory cache
Previous Message Pavel Stehule 2010-06-23 19:51:26 Re: PostgreSQL as a local in-memory cache