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

proposal: Set effective_cache_size to greater of .conf value, shared_buffers

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Date: 2013-01-08 14:39:09
Message-ID: CAHyXU0weDECnab1pypNum-dWGwjso_XMTY8-NvvzRphzM2Hv5A@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Reference: http://postgresql.1045698.n5.nabble.com/Simple-join-doesn-t-use-index-td5738689.html

This is a pretty common gotcha: user sets shared_buffers but misses
the esoteric but important effective_cache_size.  ISTM
effective_cache_size should always be >= shared buffers -- this is a
soft configuration error that could be reported as a warning and
perhaps overridden on the fly.

merlin


Responses

pgsql-hackers by date

Next:From: Claudio FreireDate: 2013-01-08 14:51:06
Subject: Re: Improve compression speeds in pg_lzcompress.c
Previous:From: Andres FreundDate: 2013-01-08 14:31:14
Subject: Re: Extra XLOG in Checkpoint for StandbySnapshot

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