Re: doc: Document Linux cgroup memory limits

From: Takeshi Ideriha <iderihatakeshi(at)gmail(dot)com>
To: Manu <manuelreyesbravo(at)gmail(dot)com>, Joao Detomini <joao(dot)detomini(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
Subject: Re: doc: Document Linux cgroup memory limits
Date: 2026-10-20 04:19:50
Message-ID: 34245387-9ed4-48b2-96aa-4fd3964d38ee@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi João

>> Attached v5 softens that sentence and recommends leaving a safety
>> margin below the limit, the same way the work_mem docs put it.

Thank you for updating a patch and adding information about cgroup might
be helpful.

Here are some comments.

I noticed some of the topics are already written in the above
'overcommit' section. For example, how to tune memory related parameters
and how postgres behaves after OOM killer terminates postgresql.
(I did small fix related to this topic in [1])

So I would do either of the followings:
1. Create a new section for cgroup as you did and only add some
references to overcommit section like "Please see the overcommit section
to decrease the risk of OOM by tuning memory parameters"

Or
2. Not create a new dedicated section for cgroup and just add "Note"
sub-section under the overcommit section, then write some peculiar
things for cgroup.

What do you think?

[1]
https://www.postgresql.org/message-id/ce269321-a7f4-48f4-a9ca-a4a4983b9fd6%40gmail.com

Regards,
Takeshi Ideriha

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sho Ito 2026-10-20 04:30:13 Re: [PATCH v1] Fix tab completion for DROP INDEX CONCURRENTLY
Previous Message Peter Smith 2026-10-20 04:02:27 Re: DOCS - CREATE PUBLICATION wording re 'ONLY' for partitioned tables.