Re: PANIC: could not flush dirty data: Cannot allocate memory - Mailing list pgsql-general

From Andres Freund
Subject Re: PANIC: could not flush dirty data: Cannot allocate memory
Date
Msg-id 20221116172838.aow3nhasrs7jwoxs@awork3.anarazel.de
Whole thread Raw
In response to Re: PANIC: could not flush dirty data: Cannot allocate memory  (Andres Freund <andres@anarazel.de>)
List pgsql-general
Hi,

On 2022-11-16 09:16:56 -0800, Andres Freund wrote:
> On 2022-11-15 13:23:56 +0100, klaus.mailinglists@pernau.at wrote:
> > Filesystem is ext4. VM technology is mixed: VMware, KVM and XEN PV. Kernel
> > is 5.15.0-52-generic.
> > 
> > We have not seen this with Ubutnu 18.04 and 20.04 (although we might not
> > have noticed it).
> 
> Did this start after upgrading to 22.04? Or after a certain kernel upgrade?
> 
> Do you use cgroups or such to limit memory usage of postgres?
> 
> I'd be helpful to see /proc/meminfo from one of the affected instances.

Another interesting thing would be to know the mount and file system options
for the FS that triggers the failures. E.g.
  tune2fs -l path/to/blockdev
and
  grep path/to/blockdev /proc/mounts

Greetings,

Andres Freund



pgsql-general by date:

Previous
From: Andres Freund
Date:
Subject: Re: PANIC: could not flush dirty data: Cannot allocate memory
Next
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL server "idle in transaction"