| From: | Joao Detomini <joao(dot)detomini(at)enterprisedb(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Umar Hayat <postgresql(dot)wizard(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Exposing the cgroup memory limit to SQL? |
| Date: | 2026-10-04 21:22:20 |
| Message-ID: | CABH8dKytV-h0x7jD4-ku-JricFrqyCTc3ArHOLZQ53Nu_-HS5A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Thanks, I hadn't come across pgnodemx. cgroup_scalar_bigint('memory.max')
covers what I had in mind, so I'll drop the idea of a function in core.
Em dom., 4 de out. de 2026 às 15:58, Joe Conway <mail(at)joeconway(dot)com>
escreveu:
> On 10/1/26 23:05, Umar Hayat wrote:
> > Hi,
> > There is the PostgreSQL wiki page "Cgroups"[1] explaining the problem
> > statement and also potential issues for implementation.
> > Seems like nobody proposed any implementation for cgroups yet
> >
> > Regards
> > Umar Hayat
> >
> > [1] https://wiki.postgresql.org/wiki/Cgroups
>
>
> This is not in the postgres tree, but I think it does what you are
> looking for (plus a lot more): https://github.com/pgnodemx/pgnodemx
>
> --
> Joe Conway
> PostgreSQL Contributors Team
> Amazon Web Services: https://aws.amazon.com
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joao Detomini | 2026-10-04 21:36:25 | Limiting WAL retained for archiving, like max_slot_wal_keep_size |
| Previous Message | Joao Detomini | 2026-10-04 21:15:59 | Re: doc: Document Linux cgroup memory limits |