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

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Dave Youatt <dave(at)fyreball(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: linux, memory (mis)accounting/reporting, and the planner/optimizer
Date: 2009-01-22 00:02:43
Message-ID: Pine.GSO.4.64.0901211859100.4605@westnet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Thomas Finneid 2009-01-22 06:23:38 caching indexes and pages?
Previous Message Dave Youatt 2009-01-21 22:01:41 linux, memory (mis)accounting/reporting, and the planner/optimizer