Re: Limit allocated memory per session
От | Robert Haas |
---|---|
Тема | Re: Limit allocated memory per session |
Дата | |
Msg-id | 603c8f070910010850k549f8d80nc940e82ebbe768f2@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Limit allocated memory per session (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Limit allocated memory per session
Re: Limit allocated memory per session |
Список | pgsql-hackers |
On Thu, Oct 1, 2009 at 11:47 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Euler Taveira de Oliveira <euler@timbira.com> writes: >> Tom Lane escreveu: >>> daveg <daveg@sonic.net> writes: >>>> I'd like to propose adding a new GUC to limit the amount of memory a backend >>>> can allocate for its own use. >>> >>> Use ulimit. >>> >> What about plataforms (Windows) that don't have ulimit? > > Get a real operating system ;-) > > Seriously, the proposed patch introduces overhead into a place that is > already a known hot spot, in return for not much of anything. It will > *not* bound backend memory use very accurately, because there is no way > to track raw malloc() calls. And I think that 99% of users will not > find it useful. What WOULD be useful is to find a way to provide a way to configure work_mem per backend rather than per executor node. But that's a much harder problem. ...Robert
В списке pgsql-hackers по дате отправления: