Greetings,
* Piotr Włodarczyk (piotrwlodarczy...@gmail.com) wrote:
> We met unexpected PostgreSQL shutdown. After a little investigation we've
> discovered that problem is in OOM killer which kills our PostgreSQL.
You need to configure your system to not overcommit.
Read up on overcommit_ratio a
What postgres version ? What environment (RAM) and config ?
https://wiki.postgresql.org/wiki/Server_Configuration
I think you can probably find more info in dmesg/syslog ; probably a
line saying "OOM killed ..." showing which PID and its vsz.
Are you able to see some particular process continuou
Maybe your memory budget does not meet the RAM on the machine?
The problem is not in the query you are looking for, but in the settings you
are using for Postgres.
regards,
fabio pardi
On 20/05/2020 09:30, Piotr Włodarczyk wrote:
> Hi folks,
>
> We met unexpected PostgreSQL shutdown. After a
Nothing special. I'll check it agin after next dead
On Wed, May 20, 2020 at 10:22 AM Laurenz Albe
wrote:
> On Wed, 2020-05-20 at 09:30 +0200, Piotr Włodarczyk wrote:
> > We met unexpected PostgreSQL shutdown. After a little investigation
> > we've discovered that problem is in OOM killer which k
On Wed, 2020-05-20 at 09:30 +0200, Piotr Włodarczyk wrote:
> We met unexpected PostgreSQL shutdown. After a little investigation
> we've discovered that problem is in OOM killer which kills our PostgreSQL.
> Unfortunately we can't find query on DB causing this problem. Log is as below:
Is there no
Hi folks,
We met unexpected PostgreSQL shutdown. After a little investigation we've
discovered that problem is in OOM killer which kills our PostgreSQL.
Unfortunately we can't find query on DB causing this problem. Log is as
below:
May 05 09:05:33 HOST kernel: postgres invoked oom-killer: gfp_mas
