Re: Estimating HugePages Requirements?

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Don Seiler <don(at)seiler(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Estimating HugePages Requirements?
Date: 2021-08-27 19:27:18
Message-ID: 071DC95B-4CA8-4D2B-BD24-1A66B3EFFE28@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On 8/27/21, 11:16 AM, "Bossart, Nathan" <bossartn(at)amazon(dot)com> wrote:
> I added some documentation in v4.

I realized that my attempt at documenting this new option was missing
some important context about the meaning of the return value when used
against a running server. I added that in v5.

Nathan

Attachment Content-Type Size
v5-0001-introduce-option-for-retreiving-shmem-size.patch application/octet-stream 13.7 KB

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andres Freund 2021-08-27 19:38:13 Re: Estimating HugePages Requirements?
Previous Message Andres Freund 2021-08-27 18:46:48 Re: Estimating HugePages Requirements?

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-08-27 19:28:42 Re: [PATCH] Disable bgworkers during servers start in pg_upgrade
Previous Message Andres Freund 2021-08-27 19:24:46 Re: Queries that should be canceled will get stuck on secure_write function