TonyS <tony@xxxxxxxxxxxxxxxxxxx> wrote:
> The postgresql log has these entries at the crash point:
> 2015-04-01 06:24:37 EDT LOG: server process (PID 1384) was terminated by signal 9: Killed
> 2015-04-01 06:24:38 EDT DETAIL: Failed process was running: analyze verbose;
That was almost certainly the action of the OS's Out Of Memory
Killer process.
> Is there anything else that would be helpful?
Unfortunately, leaving the OOM killer enabled causes the best
evidence to be destroyed. If you disable the OOM killer and run
this again, when memory is exhausted the database process
attempting to allocate memory will dump a map of where its memory
was allocated. That should give us something to work with
regarding the cause. Try:
vm.overcommit_memory = 2
vm.overcommit_ratio = 80
Also, it would be useful to see the output of this:
SELECT name, current_setting(name), source
FROM pg_settings
WHERE source NOT IN ('default', 'override');
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
