From: | Ryan Kelly <rpkelly22(at)gmail(dot)com> |
---|---|
To: | "David M(dot) Kaplan" <david(dot)kaplan(at)ird(dot)fr> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: problem with lost connection while running long PL/R query |
Date: | 2013-05-16 13:35:19 |
Message-ID: | 20130516133519.GA18133@llserver.lakeliving.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, May 05/16/13, 2013 at 02:47:28PM +0200, David M. Kaplan wrote:
> Hi,
>
> I have a query that uses a PL/R function to run a statistical model
> on data in a postgresql table. The query runs the function 4 times,
> each of which generates about 2 million lines of results, generating
> a final table that has about 8 million lines. Each time the
> function is called, it takes about ~3-5 minutes to finish its work.
> I know that the function is running fine as it gives me progress and
> I have had no trouble using it on slightly smaller datasets.
> However, this time it does the 4 runs, but ends with psql saying the
> connection to the server has been lost. In the postgresql log file,
> I have:
>
> 2013-05-16 14:05:47 CEST LOG: server process (PID 27488) was terminated by signal 9: Killed
This usually indicates the OOM killer has killed your backend. Please
see the documentation here:
http://www.postgresql.org/docs/9.2/interactive/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT
-Ryan
From | Date | Subject | |
---|---|---|---|
Next Message | Ioana Danes | 2013-05-16 13:35:39 | Re: Running out of memory at vacuum |
Previous Message | Ioana Danes | 2013-05-16 13:27:02 | Re: Running out of memory on vacuum |