From: Tom Lane <tgl@sss.pgh.pa.us>
To: zubkov318@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16659: postgresql leaks memory or do not limit its usage
Date: Wed, 07 Oct 2020 13:06:34 -0400
Message-ID: <2233626.1602090394@sss.pgh.pa.us> (raw)
In-Reply-To: <16659-2fdaaf7b4e591df9@postgresql.org>
References: <16659-2fdaaf7b4e591df9@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> I migrated a database from postgresql 10.14 in a container to
> postgres:13-alpine in docker. After a migration I see that postgresql
> processes alltogether eat memory without limits until OOM comes.
Not much to go on here. If you have debug symbols available, maybe
you could attach gdb to one of the bloated processes and do
call MemoryContextStats(TopMemoryContext)
which'd produce a memory usage report on the server's stderr.
Another idea is to start the server under a smaller ulimit,
in hopes of getting ENOMEM failures before reaching the point
of triggering OOM kills. That would also result in memory
usage reports, so you could get one even if it's a non-debug
build.
Otherwise, we'll have to ask for a reproducible test case ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, zubkov318@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16659: postgresql leaks memory or do not limit its usage
In-Reply-To: <2233626.1602090394@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox