From: | reid(dot)thompson(at)crunchydata(dot)com |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
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-03-02 19:41:26 |
Message-ID: | 1a136d92e53eea52a4cde2163918ea91cf75e0b6.camel@crunchydata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2023-02-13 at 16:26 -0800, Andres Freund wrote:
> Hi,
>
> The tests recently started to fail:
>
> https://cirrus-ci.com/github/postgresql-cfbot/postgresql/commitfest%2F42%2F3867
>
> I marked this as waiting on author.
>
> Greetings,
>
> Andres Freund
Patch has been rebased to master.
The memory limiting portion (patch 0002-*) has been refactored to utilize a
shared counter for total memory allocation along with backend-local
allowances that are initialized at process startup and refilled from the
central counter upon being used up. Free'd memory is accumulated and
returned to the shared counter upon meeting a threshold and/or upon process
exit. At this point arbitrarily picked 1MB as the initial allowance and
return threshold.
Thanks,
Reid
Attachment | Content-Type | Size |
---|---|---|
0002-Add-the-ability-to-limit-the-amount-of-memory-that-c.patch | text/x-patch | 42.4 KB |
0001-Add-tracking-of-backend-memory-allocated-to-pg_stat_.patch | text/x-patch | 33.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeroen Vermeulen | 2023-03-02 19:44:48 | Re: libpq: PQgetCopyData() and allocation overhead |
Previous Message | Tom Lane | 2023-03-02 19:36:43 | Re: Operation log for major operations |