From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mohammed Afsar <mohammed.afsar7799@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Postgresql background writer and checkpointer memory utilization
 in Linux server
In-reply-to: 
 <CA+s2FCNdjKVgwT49bFei03kzwEPrdCW8A2RhYzpbRMHzQ2XjmA@mail.gmail.com>
References: 
 <CA+s2FCOB-HKRf9G2KeB66arqTUQjKbKfJLa7D3P8wPoxwXd00Q@mail.gmail.com>
 <3398104.1597159685@sss.pgh.pa.us>
 <CA+s2FCNdjKVgwT49bFei03kzwEPrdCW8A2RhYzpbRMHzQ2XjmA@mail.gmail.com>
Comments: In-reply-to Mohammed Afsar <mohammed.afsar7799@gmail.com>
	message dated "Tue, 11 Aug 2020 21:05:11 +0530"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3398630.1597160421.1@sss.pgh.pa.us>
Date: Tue, 11 Aug 2020 11:40:21 -0400
Message-ID: <3398631.1597160421@sss.pgh.pa.us>
Precedence: bulk

Mohammed Afsar <mohammed.afsar7799@gmail.com> writes:
> Thanks for response,the exact issue which am facing is when there is no
> transaction queries are happening in database checkpointer and background
> writer is continuously utilizing memory from server.

That sounds like complete nonsense.  Those processes don't execute
queries.  It's true that they'll continue to do I/O work for some
time after queries have executed in other processes, but that's normal.

I say again that you haven't offered any evidence of having a problem
to solve.  If you don't want the database to be consuming any cycles
at all, then you should shut it down.  But if you want it to do useful
work, it's designed to spread out that work, not necessarily to do it
all before a query returns results to the client.

			regards, tom lane