Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL as a local in-memory cache

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(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-29 13:32:29
Message-ID: (view raw or whole thread)
Lists: pgsql-performance
Robert Haas wrote:
> On Mon, Jun 28, 2010 at 5:57 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> The patch also documents that synchronous_commit = false has
> >> potential committed transaction loss from a database crash (as well as
> >> an OS crash).
> Is this actually true?

I asked on IRC and was told it is true, and looking at the C code it
looks true.  What synchronous_commit = false does is to delay writing
the wal buffers to disk and fsyncing them, not just fsync, which is
where the commit loss due to db process crash comes from.

  Bruce Momjian  <bruce(at)momjian(dot)us>

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

In response to


pgsql-performance by date

Next:From: Kevin GrittnerDate: 2010-06-29 14:14:13
Subject: Re: PostgreSQL as a local in-memory cache
Previous:From: Merlin MoncureDate: 2010-06-29 13:18:14
Subject: Re: pgbench results on a new server

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group