Re: configurability of OOM killer

From: "Markus Bertheau" <mbertheau(dot)pg(at)googlemail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Dawid Kuroczko" <qnex42(at)gmail(dot)com>, "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, Decibel! <decibel(at)decibel(dot)org>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "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 02:45:37
Message-ID: 684362e10802071845o3f4dd58auf1398c5aab40a56c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2008/2/8, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> > On Thu, Feb 07, 2008 at 08:22:42PM +0100, Dawid Kuroczko wrote:
> >> ....while we are at it -- one feature would be great for 8.4, an
> >> ability to shange shared buffers size "on the fly".
>
> > Shared memory segments can't be resized... There's not even a kernel
> > API to do it.
>
> Even if there were, it seems unlikely that we could reallocate shared
> memory without stopping all active transactions, so it'd be barely less
> invasive than a postmaster restart anyhow.

What about allowing shared_buffers to be only greater than it was at server
start and allocating the extra shared_buffers in one or more additional shm
segments?

Markus

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jignesh K. Shah 2008-02-08 03:15:16 Re: Why are we waiting?
Previous Message Joshua D. Drake 2008-02-08 02:40:37 Re: 8.3 / 8.2.6 restore comparison