Re: PANIC: could not flush dirty data: Cannot allocate memory

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: PANIC: could not flush dirty data: Cannot allocate memory
Дата
Msg-id 20221116171656.3ywgpjktw5oomvec@awork3.anarazel.de
обсуждение исходный текст
Ответ на Re: PANIC: could not flush dirty data: Cannot allocate memory  (klaus.mailinglists@pernau.at)
Ответы Re: PANIC: could not flush dirty data: Cannot allocate memory  (Andres Freund <andres@anarazel.de>)
Список pgsql-general
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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: unrecognized node type: 350
Следующее
От: Andres Freund
Дата:
Сообщение: Re: PANIC: could not flush dirty data: Cannot allocate memory