Re: Postgres server crash

Поиск
Список
Период
Сортировка
Искать
От
Markus Schaber
Тема
Re: Postgres server crash
Дата
Msg-id
4562FDA0.6060602@logix-tt.com
Ответ на
Список
Дерево обсуждения
Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance Markus Schaber <schabi@logix-tt.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance Markus Schaber <schabi@logix-tt.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Michael Artz" <mlartz@gmail.com>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance Teemu Torma <teemu@torma.org>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Joshua D. Drake" <jd@commandprompt.com>
Re: Best COPY Performance "Craig A. James" <cjames@modgraph-usa.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Craig A. James" <cjames@modgraph-usa.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Craig A. James" <cjames@modgraph-usa.com>
Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Russell Smith <mr-russ@pws.com.au>
Re: Postgres server crash Richard Huxton <dev@archonet.com>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres server crash Richard Troy <rtroy@ScienceTools.com>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Bruno Wolff III <bruno@wolff.to>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Richard Broersma Jr <rabroersma@yahoo.com>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash "Jim C. Nasby" <jim@nasby.net>
Re: Postgres server crash Michael Stone <mstone+postgres@mathom.us>
Re: Postgres server crash Florian Weimer <fw@deneb.enyo.de>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres server crash Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Postgres server crash Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: Postgres server crash Markus Schaber <schabi@logix-tt.com>
Re: Postgres server crash Richard Huxton <dev@archonet.com>
Re: Postgres server crash Ben <bench@silentmedia.com>
Re: Postgres server crash "Craig A. James" <cjames@modgraph-usa.com>
Re: Postgres server crash Richard Huxton <dev@archonet.com>
Re: Postgres server crash Tom Lane <tgl@sss.pgh.pa.us>
Re: Postgres server crash "Merlin Moncure" <mmoncure@gmail.com>
Re: Best COPY Performance "Worky Workerson" <worky.workerson@gmail.com>
Re: Best COPY Performance "Jim C. Nasby" <jim@nasby.net>
Re: Best COPY Performance "Luke Lonergan" <llonergan@greenplum.com>
Re: Best COPY Performance Alex Stapleton <alexs@advfn.com>
Hi, Richard,

Richard Troy wrote:

> The reason I spent a couple of hours looking for what I could learn on
> this is that I've been absolutely beside myself on this "extremely
> unfortunate" "feature." I had a badly behaving app (but didn't know which
> app it was), so Linux would kill lots of things, like, oh, say, inetd.

Actually, AFAICT, Linux tries to kill the process(es) that use the most
memory ressources first.

Without overcommitment, the OOM killer won't kick in, and as long as the
hoggy applications don't actually exit when malloc fails, they will just
stay around, sitting on their memory.

> Good luck sshing into the box.

SSH'ing into the box will even get worse without overcommitment. When
the machine is stuck, the sshd that tries to spawn its child will get
the out of memory signal, and you won't be able to log in.

HTH,
Markus

-- 
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
В списке pgsql-performance по дате отправления
От: Mattias Kregert
Дата:
Сообщение: Re: Postgres server crash
От: Jérôme BENOIS
Дата:
FAQ