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 ) id 1pjJsw-0002Vx-C2 for pgsql-general@arkaria.postgresql.org; Mon, 03 Apr 2023 13:06:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pjJsv-0004Uz-8S for pgsql-general@arkaria.postgresql.org; Mon, 03 Apr 2023 13:06:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pjJsu-0004Uq-U2 for pgsql-general@lists.postgresql.org; Mon, 03 Apr 2023 13:06:08 +0000 Received: from smtp.burggraben.net ([88.198.69.140]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pjJss-000dQ6-7e for pgsql-general@lists.postgresql.org; Mon, 03 Apr 2023 13:06:08 +0000 Received: from squirrel.exwg.net (p54933e3d.dip0.t-ipconnect.de [84.147.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "squirrel.exwg.net", Issuer "R3" (not verified)) by smtp.burggraben.net (Postfix) with ESMTPS id D7ACCC0031A; Mon, 3 Apr 2023 15:06:04 +0200 (CEST) Received: by squirrel.exwg.net (Postfix, from userid 1000) id 9509A4B382; Mon, 3 Apr 2023 15:06:04 +0200 (CEST) Date: Mon, 3 Apr 2023 15:06:04 +0200 From: Christoph Moench-Tegeder To: Tom Lane Cc: Jason McLaurin , pgsql-general@lists.postgresql.org Subject: Re: Very slow queries followed by checkpointer process killed with signal 9 Message-ID: References: <1077329.1680479022@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1077329.1680479022@sss.pgh.pa.us> User-Agent: Mutt/2.0.5 (2021-01-21) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ## Tom Lane (tgl@sss.pgh.pa.us): > Jason McLaurin writes: > > I'm troubleshooting an issue where about once a week, a database appears to > > lock up and then the PostgreSQL process crashes and recovers. When this > > happens, a few queries will be logged, but there is no pattern to which > > queries are executing when the crash happens, and the queries logged don't > > appear to be queries that would consume a lot of resources. > > Hmm, is it always the checkpointer that gets the OOM kill? That seems > quite odd. Are you sure it's OOM? That's a frequent source of SIGKILLs, but SIGKILL is not exclusive to oomkiller. Maybe something in the container stack (some cgroup resource limiting? would be in line with slowdown at least; or a hard ulimit on cpu time?) or maybe even some "anti virus" thingy ("It's been 0 days since AV ate the database"). Regards, Christoph -- Spare Space.