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

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 (view raw or flat)
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

pgsql-performance by date

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

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