From: | "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
---|---|
To: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Dawid Kuroczko" <qnex42(at)gmail(dot)com> |
Cc: | "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, "Decibel!" <decibel(at)decibel(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jeff Davis" <pgsql(at)j-davis(dot)com>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Pg Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: configurability of OOM killer |
Date: | 2008-02-08 09:22:12 |
Message-ID: | E1539E0ED7043848906A8FF995BDA57902C24A2F@m0143.s-mxs.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Cave-Ayland | 2008-02-08 09:54:50 | Re: PostgreSQL 8.4 development plan |
Previous Message | Markus Bertheau | 2008-02-08 09:19:29 | Re: PostgreSQL 8.4 development plan |