On Saturday, May 19, 2012 04:42:16 PM Clemens Eisserer wrote:
> Hi again,
>
> We are still constantly getting postgresql processes killed by signal
> 9 from time to time, without any idea why or how.
> Syslog seems completly clean.
>
> In case a postgresql process would exceed some restricted res
Hi again,
We are still constantly getting postgresql processes killed by signal
9 from time to time, without any idea why or how.
Syslog seems completly clean.
In case a postgresql process would exceed some restricted resources
like file descriptors, would the kernel choose to terminate it using
Hi Steve,
> Out of memory or OOM killer?? Any such messages in system logs?
That was my first thought too - but I could't find anything indicating
an OOM event in the logs.
Usually the server only uses ~110mb out of the available 2GB assigned to it.
So if this isn't a known postgres behaviour, I
On 05/17/2012 03:44 PM, Clemens Eisserer wrote:
Hi,
Recently single postgres processes are killed by SIGNAL 9 on our
virtual vvmware managed server without any manual interaction -
causing lost transactions.
Any ideas what could be the reason? Could postmaster the source of the signal?
We are r
Hi,
Recently single postgres processes are killed by SIGNAL 9 on our
virtual vvmware managed server without any manual interaction -
causing lost transactions.
Any ideas what could be the reason? Could postmaster the source of the signal?
We are running postgreql 8.4.7 on Linux 64-bit.
Thank you
