Re: linux, memory (mis)accounting/reporting, and the planner/optimizer - Mailing list pgsql-performance

From Greg Smith
Subject Re: linux, memory (mis)accounting/reporting, and the planner/optimizer
Date
Msg-id Pine.GSO.4.64.0901211859100.4605@westnet.com
Whole thread Raw
In response to linux, memory (mis)accounting/reporting, and the planner/optimizer  (Dave Youatt <dave@fyreball.com>)
Responses Re: linux, memory (mis)accounting/reporting, and the planner/optimizer  ("M. Edward (Ed) Borasky" <znmeb@cesmail.net>)
List pgsql-performance
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@gregsmith.com http://www.gregsmith.com Baltimore, MD

pgsql-performance by date:

Previous
From: Dave Youatt
Date:
Subject: linux, memory (mis)accounting/reporting, and the planner/optimizer
Next
From: "M. Edward (Ed) Borasky"
Date:
Subject: Re: linux, memory (mis)accounting/reporting, and the planner/optimizer