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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxx http://www.gregsmith.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
2.6.25.

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

-- 
M. Edward (Ed) Borasky

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

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux