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

Re: PostgreSQL as a local in-memory cache

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: PostgreSQL as a local in-memory cache
Date: 2010-06-17 19:59:39
Message-ID: 4C1A7EAB.3020202@2ndquadrant.com (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-performance
Josh Berkus wrote:
> a) Eliminate WAL logging entirely
> c) Turn off the background writer

Note that if you turn off full_page_writes and set 
bgwriter_lru_maxpages=0, you'd get a substantial move in both these 
directions without touching any code.  Would help prove those as useful 
directions to move toward or not.  The difference in WAL writes just 
after a checkpoint in particular, due to the full_page_writes behavior, 
is a significant portion of total WAL activity on most systems.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com   www.2ndQuadrant.us


In response to

pgsql-performance by date

Next:From: Pierre CDate: 2010-06-17 20:12:25
Subject: Re: PostgreSQL as a local in-memory cache
Previous:From: Tom LaneDate: 2010-06-17 19:38:30
Subject: Re: PostgreSQL as a local in-memory cache

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