michael, 2 months ago

@K9MAX it means you don’t have enough free memory.

K9MAX, 2 months ago

@michael That‘s what I thought too. However - database size is approximately 1.8 GB and RAM is 16GB at the moment. For a dump it should be sufficient - or not? Can you recommend something which I can do (e. g. stop everything except postgresql) and retry the dump? I would like to avoid upgrading the server now.

michael, 2 months ago

@K9MAX what else is consuming memory on that server? htop might be able to tell you.

But yes, theoretically if you stop everything but postgres you might have better chances.

K9MAX, 2 months ago

@michael Elasticsearch is running on the same machine with a memory limit of 4GB. I stopped elasticsearch but got the same error message.

michael, 2 months ago

@K9MAX what’s the output of free -h?

K9MAX, 2 months ago

@michael Good morning!
This is what free -h is telling me:
total 15Gi
used 6.4Gi
free 6.2Gi
shared 1.5Gi
buff/cache 3.0Gi
available 7.4Gi

This should be enough to run a dump I guess. The worst situation would then be a corrupted table.

michael, 2 months ago

@K9MAX have a look at what @nik suggested yesterday: I think their comment might be more helpful than mine:

https://toot.teckids.org/@nik/112226437317415309