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 1ov3Iw-00078X-4X for pgsql-general@arkaria.postgresql.org; Tue, 15 Nov 2022 21:17:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ov3Iu-00050I-Nh for pgsql-general@arkaria.postgresql.org; Tue, 15 Nov 2022 21:17:12 +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 ) id 1ov3Iu-000508-DH for pgsql-general@lists.postgresql.org; Tue, 15 Nov 2022 21:17:12 +0000 Received: from smtp.burggraben.net ([2a01:4f8:140:510a::3]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ov3Ir-0003xi-LE for pgsql-general@postgresql.org; Tue, 15 Nov 2022 21:17:11 +0000 Received: from elch.exwg.net (elch.exwg.net [IPv6:2001:470:7120:1:127b:44ff:fe4f:148d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "elch.exwg.net", Issuer "R3" (not verified)) by smtp.burggraben.net (Postfix) with ESMTPS id AB389C011E0; Tue, 15 Nov 2022 22:17:05 +0100 (CET) Received: by elch.exwg.net (Postfix, from userid 1000) id 40F303AB04; Tue, 15 Nov 2022 22:17:05 +0100 (CET) Date: Tue, 15 Nov 2022 22:17:05 +0100 From: Christoph Moench-Tegeder To: klaus.mailinglists@pernau.at Cc: pgsql-general@postgresql.org Subject: Re: PANIC: could not flush dirty data: Cannot allocate memory Message-ID: References: <7e02611b56aebc62a0ec25bb39687491@pernau.at> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7e02611b56aebc62a0ec25bb39687491@pernau.at> User-Agent: Mutt/2.2.9 (2022-11-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ## klaus.mailinglists@pernau.at (klaus.mailinglists@pernau.at): > AFAIU the problem is not related to the memory settings in > postgresql.conf. It is the kernel that > for whatever reasons report ENOMEM. Correct? Correct, there's a ENOMEM from the kernel when writing out data. > Filesystem is ext4. VM technology is mixed: VMware, KVM and XEN PV. > Kernel is 5.15.0-52-generic. I do not suspect the filesystem per se, ext4 is quite common and we would have heard something about that (but then, someone gotta be the first reporter?). I would believe that the kernel would raise a bunch of printks if it hit ENOMEM in the commonly used paths, so you would see something in dmesg or wherever you collect your kernel log if it happened where it was expected. And coming from the other side: does this happen on all the hosts, or is it limited to one host or one technology? Any uncommon options on the filesystem or the mount point? Anything which could mess with your block devices? (I'm expecially thinking "antivirus" because it's always "0 days since the AV ate a database" and they tend to raise errors in the weirdest places, which would fit the bill here; but anythig which is not "commonly in use everywhere" could be a candidate). Regards, Christoph -- Spare Space