Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1jxeMq-0004Rj-EV
	for pgsql-admin@arkaria.postgresql.org; Mon, 20 Jul 2020 22:34:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1jxeMp-0007D4-26
	for pgsql-admin@arkaria.postgresql.org; Mon, 20 Jul 2020 22:34:39 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jxeMo-0007Cv-Qd
	for pgsql-admin@lists.postgresql.org; Mon, 20 Jul 2020 22:34:38 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jxeMi-00055j-Cl
	for pgsql-admin@postgresql.org; Mon, 20 Jul 2020 22:34:37 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 06KMYPjR736812;
	Mon, 20 Jul 2020 18:34:25 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: jian xu <jamesxu@outlook.com>
cc: MichaelDBA <MichaelDBA@sqlexec.com>,
        Scott Ribe <scott_ribe@elevated-dev.com>,
        Laurenz Albe <laurenz.albe@cybertec.at>,
        "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: checkpoint process use too much memory
In-reply-to: 
 <DM6PR05MB68270B6144BDF688D3849436A17B0@DM6PR05MB6827.namprd05.prod.outlook.com>
References: 
 <MN2PR05MB68322593E34D4BF78AD45137A1D70@MN2PR05MB6832.namprd05.prod.outlook.com>
 <5193b00d175f2e06a171ba375f1ef723e1700de4.camel@cybertec.at>
 <MN2PR05MB6832AA29B8D72FCA59D29E19A1D40@MN2PR05MB6832.namprd05.prod.outlook.com>
 <C7D8AF88-5A80-4F1E-B3AF-7BB01369FD87@elevated-dev.com>
 <MN2PR05MB6832881823D2B12D767C8C67A1D40@MN2PR05MB6832.namprd05.prod.outlook.com>
 <B2103F5D-29DD-465C-A43B-9973EC313799@elevated-dev.com>,<fcb5bde4-437d-913e-cb1f-3fdb866a805a@sqlexec.com>,<MN2PR05MB68327F7153695ED742BF1B19A1D50@MN2PR05MB6832.namprd05.prod.outlook.com>
 <DM6PR05MB68270B6144BDF688D3849436A17B0@DM6PR05MB6827.namprd05.prod.outlook.com>
Comments: In-reply-to jian xu <jamesxu@outlook.com>
	message dated "Mon, 20 Jul 2020 21:33:55 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <736810.1595284465.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Jul 2020 18:34:25 -0400
Message-ID: <736811.1595284465@sss.pgh.pa.us>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

jian xu <jamesxu@outlook.com> writes:
>       we are seeing this issue again, the checkpoint process is eating u=
p all the memory,
> based on the htop, the checkpointer process has
> VIRT: 103G
> RES: 103G
> SHR: 4099M

hmmm ...

> my pg version is 10.3 ,

Really the *first* thing you ought to do is update to current (10.13)
and see if the problem is still there.  But if it is, maybe collecting
a memory context map in that process would be informative:

https://wiki.postgresql.org/wiki/Developer_FAQ#Examining_backend_memory_us=
e

Note you may need a debug build for that recipe to work.

			regards, tom lane