| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Reid Thompson <reid(dot)thompson(at)crunchydata(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Arne Roland <A(dot)Roland(at)index(dot)de>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com> |
| Subject: | Re: Add the ability to limit the amount of memory that can be allocated to backends. |
| Date: | 2023-02-14 00:26:27 |
| Message-ID: | 20230214002627.7btgrc34forjkm2i@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2023-01-26 15:27:20 -0500, Reid Thompson wrote:
> Yes, just a rebase. There is still work to be done per earlier in the
> thread.
The tests recently started to fail:
https://cirrus-ci.com/github/postgresql-cfbot/postgresql/commitfest%2F42%2F3867
> I do want to follow up and note re palloc/pfree vs malloc/free that the
> tracking code (0001-Add-tracking-...) is not tracking palloc/pfree but is
> explicitely tracking malloc/free. Not every palloc/pfree call executes the
> tracking code, only those where the path followed includes malloc() or
> free(). Routine palloc() calls fulfilled from the context's
> freelist/emptyblocks/freeblock/etc and pfree() calls not invoking free()
> avoid the tracking code.
Sure, but we create a lot of memory contexts, so that's not a whole lot of
comfort.
I marked this as waiting on author.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-02-14 00:29:57 | Re: Buffer usage detailed by RelKind in EXPLAIN ANALYZE BUFFERS |
| Previous Message | Andrey Borodin | 2023-02-14 00:23:30 | Buffer usage detailed by RelKind in EXPLAIN ANALYZE BUFFERS |