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

From Robert Haas
Subject Re: PostgreSQL as a local in-memory cache
Date
Msg-id AANLkTimOEFqtvOrSB_iZDBLjywIqNqeDy61JJEU689M5@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL as a local in-memory cache  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PostgreSQL as a local in-memory cache
List pgsql-performance
On Tue, Jun 29, 2010 at 9:32 AM, Bruce Momjian <bruce@momjian.us> wrote:
> Robert Haas wrote:
>> On Mon, Jun 28, 2010 at 5:57 PM, Bruce Momjian <bruce@momjian.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.

Ah, I see.  Thanks.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-performance by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: cpu bound postgresql setup.
Next
From: Bruce Momjian
Date:
Subject: Re: PostgreSQL as a local in-memory cache