Postgres Pro
Downloads
Home   >   mailing lists

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 20221116171656.3ywgpjktw5oomvec@awork3.anarazel.de
Whole thread Raw
In response to Re: PANIC: could not flush dirty data: Cannot allocate memory  (klaus.mailinglists@pernau.at)
Responses Re: PANIC: could not flush dirty data: Cannot allocate memory
List pgsql-general
Tree view 
Hi,

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.

Greetings,

Andres Freund

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: unrecognized node type: 350
Next
From: Andres Freund
Date:
Subject: Re: PANIC: could not flush dirty data: Cannot allocate memory