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 24597.1276803510@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL as a local in-memory cache  (Dimitri Fontaine)
Responses Re: PostgreSQL as a local in-memory cache  (Bruce Momjian)
Re: PostgreSQL as a local in-memory cache  (Bruce Momjian)
List pgsql-performance
Dimitri Fontaine <> writes:
> Josh Berkus <> writes:
>> a) Eliminate WAL logging entirely
>> b) Eliminate checkpointing
>> c) Turn off the background writer
>> d) Have PostgreSQL refuse to restart after a crash and instead call an
>> exteral script (for reprovisioning)

> Well I guess I'd prefer a per-transaction setting, allowing to bypass
> WAL logging and checkpointing.

Not going to happen; this is all or nothing.

> Forcing the backend to care itself for
> writing the data I'm not sure is a good thing, but if you say so.

Yeah, I think proposal (c) is likely to be a net loss.

(a) and (d) are probably simple, if by "reprovisioning" you mean
"rm -rf $PGDATA; initdb".  Point (b) will be a bit trickier because
there are various housekeeping activities tied into checkpoints.
I think you can't actually remove checkpoints altogether, just
skip the flush-dirty-pages part.

            regards, tom lane

pgsql-performance by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: PostgreSQL as a local in-memory cache
Next
From: Greg Smith
Date:
Subject: Re: PostgreSQL as a local in-memory cache