Re: Postgres server crash

Поиск
Список
Период
Сортировка
Искать
От
Craig A. James
Тема
Re: Postgres server crash
Дата
Msg-id
455FFD02.1060503@modgraph-usa.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>
Richard Troy wrote:
> I did that - spent about two f-ing hours looking for what I wanted. (Guess
> I entered poor choices for my searches. -frown- ) There are a LOT of
> articles that TALK ABOUT OOM, but prescious few actually tell you what you
> can do about it.
> 
> Trying to save you some time:
> 
> On linux you can use the sysctl utility to muck with vm.overcommit_memory;
> You can disable the "feature."
> 
> Google _that_ for more info!


Here's something I found googling for "memory overcommitment"+linux

  http://archives.neohapsis.com/archives/postfix/2000-04/0512.html

  From /usr/src/linux/Documentation/sysctl/vm.txt

  "overcommit_memory:

  This value contains a flag that enables memory overcommitment.
  When this flag is 0, the kernel checks before each malloc()
  to see if there's enough memory left. If the flag is nonzero,
  the system pretends there's always enough memory."

  This flag is settable in /proc/sys/vm

Lo and behold, here it is on my system:

   $ cat /proc/sys/vm/overcommit_memory
   0
   $ cat /proc/sys/vm/overcommit_ratio 
   50

Craig
В списке pgsql-performance по дате отправления
От: rakesh kumar
Дата:
Сообщение: Fwd: start up cost estimate
От: Tom Lane
Дата:
Сообщение: Re: Postgres server crash
FAQ