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

From Jonathan Gardner
Subject Re: PostgreSQL as a local in-memory cache
Date
Msg-id AANLkTilVMJK-XpFpTNltc0OED-q8cMlGCvh7Wy8A_mhq@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL as a local in-memory cache  (Josh Berkus <josh@agliodbs.com>)
Responses Re: PostgreSQL as a local in-memory cache  (Balkrishna Sharma <b_ki@hotmail.com>)
List pgsql-performance
On Wed, Jun 16, 2010 at 12:00 PM, Josh Berkus <josh@agliodbs.com> wrote:
>
>> * fsync=off => 5,100
>> * fsync=off and synchronous_commit=off => 5,500
>
> Now, this *is* interesting ... why should synch_commit make a difference
> if fsync is off?
>
> Anyone have any ideas?
>

I may have stumbled upon this by my ignorance, but I thought I read
that synchronous_commit controlled whether it tries to line up commits
or has a more free-for-all that may cause some intermediate weirdness.

--
Jonathan Gardner
jgardner@jonathangardner.net

pgsql-performance by date:

Previous
From: Jonathan Gardner
Date:
Subject: Re: PostgreSQL as a local in-memory cache
Next
From: "Kevin Grittner"
Date:
Subject: Re: Confirm calculus