Re: Built-in support for a memory consumption ulimit?
От | Robert Haas |
---|---|
Тема | Re: Built-in support for a memory consumption ulimit? |
Дата | |
Msg-id | CA+TgmoYvtxt6toA4EzjxVFkBzXk0cKzuU_2tiCNQntPtf_2iCA@mail.gmail.com обсуждение исходный текст |
Ответ на | Built-in support for a memory consumption ulimit? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Built-in support for a memory consumption ulimit?
Re: Built-in support for a memory consumption ulimit? |
Список | pgsql-hackers |
On Sat, Jun 14, 2014 at 10:37 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > After giving somebody advice, for the Nth time, to install a > memory-consumption ulimit instead of leaving his database to the tender > mercies of the Linux OOM killer, it occurred to me to wonder why we don't > provide a built-in feature for that, comparable to the "ulimit -c max" > option that already exists in pg_ctl. A reasonably low-overhead way > to do that would be to define it as something a backend process sets > once at startup, if told to by a GUC. The GUC could possibly be > PGC_BACKEND level though I'm not sure if we want unprivileged users > messing with it. > > Thoughts? What happens if the limit is exceeded? ERROR? FATAL? PANIC? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: