| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
| 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 13:57:27 |
| Message-ID: | 1183741.1595944647@sss.pgh.pa.us |
| 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:
> we have a very strange behavior on PostgreSQL 12.3 when we try to create the extension postgis. Postgres and postgis have both been installed from packages:
> ...
> 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)
Quite odd. There should have been a memory context dump written to the
postmaster's stderr, can you show that? Also possibly useful would be
a backtrace (set a breakpoint at errfinish):
https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaozhong SHI | 2020-07-28 13:59:24 | Re: Issues of slow running queries when dealing with Big Data |
| Previous Message | Scott Ribe | 2020-07-28 12:28:21 | Re: is JIT available |