Re: configurability of OOM killer - Mailing list pgsql-hackers

From Zeugswetter Andreas ADI SD
Subject Re: configurability of OOM killer
Date
Msg-id E1539E0ED7043848906A8FF995BDA57902C24A2F@m0143.s-mxs.net
Whole thread Raw
In response to Re: configurability of OOM killer  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
> > ....while we are at it -- one feature would be great for 8.4, an
> > ability to shange shared buffers size "on the fly".  I expect
> > it is not trivial, but would help fine-tuning running database.
> > I think DBA would need to set maximum shared buffers size
> > along the normal setting.
>
> Shared memory segments can't be resized... There's not even a kernel
> API to do it.

Yes, but the typical way around that is to allocate additional segments.
You would want a configurable size and a limit though.
Just wanted to air this possibility, cause it seems nobody is aware
here.
It does cause all sorts of issues, but it's not like there is no way to
increase shared memory.

The dba would then reconfigure and restart at a convenient time to
reduce
the number of segments because that is typically more performant.

Andreas


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: GSSAPI and V2 protocol
Next
From: Mark Cave-Ayland
Date:
Subject: Re: PostgreSQL 8.4 development plan