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

Re: PostgreSQL as a local in-memory cache

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Josh Berkus" <josh(at)agliodbs(dot)com>, "Dimitri Fontaine" <dfontaine(at)hi-media(dot)com>, "postgres performance list" <pgsql-performance(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: PostgreSQL as a local in-memory cache
Date: 2010-06-29 14:14:13
Message-ID: 4C29B9650200002500032CC2@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-performance
Bruce Momjian <bruce(at)momjian(dot)us> wrote:
 
> What synchronous_commit = false does is to delay writing
> the wal buffers to disk and fsyncing them, not just fsync
 
Ah, that answers the question Josh Berkus asked here:
 
http://archives.postgresql.org/pgsql-performance/2010-06/msg00285.php
 
(which is something I was wondering about, too.)
 
-Kevin

In response to

pgsql-performance by date

Next:From: Benjamin KrajmalnikDate: 2010-06-29 15:11:53
Subject: Re: cpu bound postgresql setup.
Previous:From: Bruce MomjianDate: 2010-06-29 13:32:29
Subject: Re: PostgreSQL as a local in-memory cache

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