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

2022-12-05 Thread klaus . mailinglists
Some more updates Did this start after upgrading to 22.04? Or after a certain kernel upgrade? For sure it only started with Ubuntu 22.04. We did not had and still not have any issues on servers with Ubuntu 20.04 and 18.04. It also happens with Ubuntu 22.10 (Kernel 5.19.0-23-generic).

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

2022-11-29 Thread klaus . mailinglists
Hello all! Thanks for the many hints to look for. We did some tuning and further debugging and here are the outcomes, answering all questions in a single email. In the meantime, you could experiment with setting checkpoint_flush_after to 0 We did this: # SHOW checkpoint_flush_after;

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

2022-11-15 Thread klaus . mailinglists
Thanks all for digging into this problem. AFAIU the problem is not related to the memory settings in postgresql.conf. It is the kernel that for whatever reasons report ENOMEM. Correct? Am 2022-11-14 22:54, schrieb Christoph Moench-Tegeder: ## klaus.mailingli...@pernau.at

PANIC: could not flush dirty data: Cannot allocate memory

2022-11-14 Thread klaus . mailinglists
Hi all! We have a setup with a master and plenty of logical replication slaves. Master and slaves are 12.12-1.pgdg22.04+1 runnning on Ubuntu 22.04. SELECT pg_size_pretty( pg_database_size('regdns') ); is from 25GB (fresh installed slave) to 42GB (probably bloat) Replication slaves VMs have