| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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 19:37:20 |
| Message-ID: | 201006231937.o5NJbKp05127@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-06-23 19:40:08 | Re: PostgreSQL as a local in-memory cache |
| Previous Message | Scott Marlowe | 2010-06-23 19:34:33 | Re: WAL+Os on a single disk |