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 18:39:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
Greg Smith wrote:
> On Wed, 21 Jan 2009, M. Edward (Ed) Borasky wrote:
>> Re the OOM killer -- maybe a patch to the kernel could make things
>> "better"??
> People have tried to raise awareness of it; sample:
> without much success.  The Linux kernel hackers dislike the whole
> approach PostgreSQL uses to allocate shared memory anyway--witness the
> backlash against any attempt to raise SHMMAX.
> I found the long thread that beats this issue to death in the archives
> again:
> That discussion should get raised to a higher profile eventually, maybe
> a summary on the wiki.
> -- 
> * Greg Smith gsmith(at)gregsmith(dot)com Baltimore, MD
Yes, please collect as much detail as you can in some centralized place.
For recent kernels (2.6.25+) the memory accounting is much better, and
if nothing else, there might be some things PostgreSQL could do to
minimize the probability of getting hit, at the cost of some
platform-dependent (/proc reading) code. The problem is that
"enterprise" Linux distros aren't running 2.6.25+ yet. :(

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: Alvaro HerreraDate: 2009-01-22 19:00:12
Subject: Re: postgresql 8.3 tps rate
Previous:From: Simon RiggsDate: 2009-01-22 18:05:45
Subject: Re: caching written values?

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