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

Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

From: Peter van Hardenberg <pvh(at)pvh(dot)ca>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?
Date: 2012-03-02 00:28:02
Message-ID: CAAcg=kXps0_151vhQe4RYX++DUX9Z0TGVev-Gri19dZmDmnb9g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, Mar 1, 2012 at 4:23 PM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
> For a read-only database, as was discussed, a lower shared_buffers
> settings makes sense. And 128M is low enough, I'd guess.
>
> Setting work_mem to hundreds of MB in a 4G system is suicide. Tens
> even is dangerous.
>

Why do you say that? We've had work_mem happily at 100MB for years. Is
there a particular degenerate case you're concerned about?

-p

-- 
Peter van Hardenberg
San Francisco, California
"Everything was beautiful, and nothing hurt." -- Kurt Vonnegut

In response to

Responses

pgsql-performance by date

Next:From: Jeff JanesDate: 2012-03-02 00:35:23
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?
Previous:From: Claudio FreireDate: 2012-03-02 00:23:20
Subject: Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory?

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