Re: PostgreSQL as a local in-memory cache

From: Jonathan Gardner <jgardner(at)jonathangardner(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL as a local in-memory cache
Date: 2010-06-16 19:19:20
Message-ID: AANLkTilVMJK-XpFpTNltc0OED-q8cMlGCvh7Wy8A_mhq@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Jun 16, 2010 at 12:00 PM, Josh Berkus <josh(at)agliodbs(dot)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(at)jonathangardner(dot)net

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jonathan Gardner 2010-06-16 19:22:17 Re: PostgreSQL as a local in-memory cache
Previous Message Jonathan Gardner 2010-06-16 19:17:11 Re: PostgreSQL as a local in-memory cache