| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | klaus(dot)mailinglists(at)pernau(dot)at |
| Cc: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PANIC: could not flush dirty data: Cannot allocate memory |
| Date: | 2022-11-16 17:28:38 |
| Message-ID: | 20221116172838.aow3nhasrs7jwoxs@awork3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 2022-11-16 09:16:56 -0800, Andres Freund wrote:
> On 2022-11-15 13:23:56 +0100, klaus(dot)mailinglists(at)pernau(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2022-11-16 17:42:16 | Re: PostgreSQL server "idle in transaction" |
| Previous Message | Andres Freund | 2022-11-16 17:16:56 | Re: PANIC: could not flush dirty data: Cannot allocate memory |