Re: Estimating HugePages Requirements?

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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 06:46:35
Message-ID: YSiKS58gSXDpj6NR@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Wed, Aug 11, 2021 at 11:23:52PM +0000, Bossart, Nathan wrote:
> I think BootstrapModeMain() makes the most sense. It fits in nicely
> with the --check logic that's already there. With v3, the following
> command can be used to retrieve the amount of shared memory required.
>
> postgres --output-shmem -D dir
>
> While testing this new option, I noticed that you can achieve similar
> results today with the following command, although this one will
> actually try to create the shared memory, too.

That may not be the best option.

> IMO the new option is still handy, but I can see the argument that it
> might not be necessary.

A separate option looks handy. Wouldn't it be better to document it
in postgres-ref.sgml then?
--
Michael

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2021-08-27 07:29:34 Re: slave stops replica
Previous Message Pepe TD Vo 2021-08-26 21:09:20 slave stops replica

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2021-08-27 07:05:50 Re: Supply restore_command to pg_rewind via CLI argument
Previous Message Dilip Kumar 2021-08-27 06:34:31 Re: Separate out FileSet from SharedFileSet (was Re: pgsql: pgstat: Bring up pgstat in BaseInit() to fix uninitialized use o)