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

Re: linux, memory (mis)accounting/reporting, and the planner/optimizer

From: "M(dot) Edward (Ed) Borasky" <znmeb(at)cesmail(dot)net>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: Dave Youatt <dave(at)fyreball(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: linux, memory (mis)accounting/reporting, and the planner/optimizer
Date: 2009-01-22 06:23:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Greg Smith wrote:
> On Wed, 21 Jan 2009, Dave Youatt wrote:
>> Does it just accept the configuration parameters provided (e.g. --
>> shared_buffers, effective_cache_size, etc.)?
> That's it.  The only time PostgreSQL gets a report from the OS related
> to memory is if it makes an allocation attempt that fails.  Couldn't
> care less what Linux thinks the rest of the time--unless the OOM killer
> goes on a rampage, counts shared memory badly, and decides to kill a
> database process that is.
> -- 
> * Greg Smith gsmith(at)gregsmith(dot)com Baltimore, MD

The shared memory accounting in Linux got better in the 2.6.25 kernel,
although I'm not sure the user space tools are fully deployed even today
to track it. And of course, lots of servers still use kernels older than

Re the OOM killer -- maybe a patch to the kernel could make things

M. Edward (Ed) Borasky

I've never met a happy clam. In fact, most of them were pretty steamed.

In response to


pgsql-performance by date

Next:From: A. KretschmerDate: 2009-01-22 07:01:36
Subject: Re: caching indexes and pages?
Previous:From: Thomas FinneidDate: 2009-01-22 06:23:38
Subject: caching indexes and pages?

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