From: Tom Lane <tgl@sss.pgh.pa.us>
To: vihari.postgresdba@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17309: Memory consumption
Date: Thu, 02 Dec 2021 13:37:28 -0500
Message-ID: <2116851.1638470248@sss.pgh.pa.us> (raw)
In-Reply-To: <17309-5100d1a52bb9b72e@postgresql.org>
References: <17309-5100d1a52bb9b72e@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> We are configured postgres 13.2 version in the EKS cluster. We are facing
> high memory consumption. we have 60GB of RAM and with in one week almost
> the memory is reaching 40 GB. I found one of the checkpointer background
> process is consuming 16.1 % memory. I never seen this much memory
> consumption in the postgres. Please provide any option to resolve this
> memory issue. Kindly let me know if any memory leak in the postgres 13.2
> version.
It seems quite unlikely that there's any actual bug here; more likely,
you are misreading the output of "ps". Many versions of ps will report
a process's use of shared memory as though it were local memory in that
process, ie ps will claim that each process is consuming the whole amount
of the shared memory, even though there's really only one copy.
Particularly with the checkpointer, which doesn't run any user-defined
code, a leak isn't very credible. I would ask first what is your
shared_buffers setting? If the checkpointer's reported memory
consumption isn't much more than that, then there's nothing to see here.
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, vihari.postgresdba@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17309: Memory consumption
In-Reply-To: <2116851.1638470248@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