Re: Out of memory with "create extension postgis"

From: "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Out of memory with "create extension postgis"
Date: 2020-07-28 15:04:57
Message-ID: ZR0P278MB0122C24D9DEE78F10A336287D2730@ZR0P278MB0122.CHEP278.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>>> "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> writes:
>>>> The process eats all the available memory and finally dies:
>>>> # create extension postgis;
>>>> ERROR: out of memory
>>>> DETAIL: Failed on request of size 8265691 in memory context "PortalContext".
>>>> Time: 773569.877 ms (12:53.570)

>> There is nothing in the log file except these (not from today, but the messages are always the same):
>> 2020-07-03 16:52:16 CEST 53617 LOG: server process (PID 54070) was terminated by signal 9: Killed

>A process that was killed by the OOM killer would not have managed to
>produce an "out of memory" ERROR report, so these two are different
>symptoms. You need to reproduce the first case, or you won't have
>any luck setting an error breakpoint either.

You're right, that was before we adjusted the oom behavior. Will get back once I have more information.

Regards
Daniel

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Lewis 2020-07-28 15:41:56 Re: Issues of slow running queries when dealing with Big Data
Previous Message Tom Lane 2020-07-28 14:55:21 Re: Out of memory with "create extension postgis"