"Daniel Westermann (DWE)" <daniel.westermann@xxxxxxxxxxxxxxxx> writes: > So this is what we got today. In the log file there is this: > 2020-07-29 16:33:23 CEST 101995 ERROR: out of memory > 2020-07-29 16:33:23 CEST 101995 DETAIL: Failed on request of size 8265691 in memory context "PortalContext". > 2020-07-29 16:33:23 CEST 101995 STATEMENT: create extension postgis; Is there not a dump of memory context sizes just before the "ERROR: out of memory" line? It should look something like TopMemoryContext: 68720 total in 5 blocks; 17040 free (15 chunks); 51680 used MessageContext: 8192 total in 1 blocks; 6880 free (1 chunks); 1312 used ... ErrorContext: 8192 total in 1 blocks; 7928 free (3 chunks); 264 used Grand total: 1063328 bytes in 190 blocks; 312376 free (159 chunks); 750952 used (this taken from an idle backend, so numbers from a backend that's hit OOM would be a lot larger). If you don't see that then you must be using some logging mechanism that fails to capture the postmaster's stderr output, such as syslog. If your postmaster start script doesn't actually send stderr to /dev/null, you might find the context map in some other log file. > The GDB session shows this: Umm ... you didn't issue a "bt" when you got to errfinish, so there's no useful info here. > Missing separate debuginfos, use: debuginfo-install CGAL-4.7-1.rhel7.1.x86_64 boost-date-time-1.53.0-27.el7.x86_64 boost-serialization-1.53.0-27.el7.x86_64 boost-system-1.53.0-27.el7.x86_64 boost-thread-1.53.0-27.el7.x86_64 gmp-6.0.0-15.el7.x86_64 jbigkit-libs-2.0-11.el7.x86_64 json-c-0.11-4.el7_0.x86_64 libcurl-7.29.0-54.el7_7.2.x86_64 libidn-1.28-4.el7.x86_64 libjpeg-turbo-1.2.90-8.el7.x86_64 libssh2-1.8.0-3.el7.x86_64 libtiff-4.0.3-32.el7.x86_64 mpfr-3.1.1-4.el7.x86_64 postgis30_12-3.0.1-5.rhel7.x86_64 protobuf-c-1.0.2-3.el7.x86_64 sqlite33-libs-3.30.1-1.rhel7.x86_64 This is a little weird and scary; I would not expect most of those libraries to have gotten linked into a Postgres backend. What extensions are you using? (And what the devil would any of them want with sqlite or libcurl? boost-thread is even scarier, because we absolutely do not support multithreading in a backend process.) regards, tom lane
