Date: Thu, 29 Feb 2024 13:04:04 +0900 (JST)
Message-Id: <20240229.130404.1411153273308142188.horikyota.ntt@gmail.com>
To: alvherre@alvh.no-ip.org
Cc: x4mmm@yandex-team.ru, dilipbalaut@gmail.com, tndrwang@gmail.com,
 pgsql-hackers@lists.postgresql.org, tomas.vondra@enterprisedb.com
Subject: Re: SLRU optimization - configurable buffer pool and partitioning
 the SLRU lock
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
In-Reply-To: <202402271733.43375fmfpr2f@alvherre.pgsql>
References: <202402271626.ilamiem7n3hl@alvherre.pgsql>
	<202402271733.43375fmfpr2f@alvherre.pgsql>
User-Agent: Mew version 6.8 on Emacs 27.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/20240229.130404.1411153273308142188.horikyota.ntt%40gmail.com>
Precedence: bulk

At Tue, 27 Feb 2024 18:33:18 +0100, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote in 
> Here's the complete set, with these two names using the singular.

The commit by the second patch added several GUC descriptions:

> Sets the size of the dedicated buffer pool used for the commit timestamp cache.

Some of them, commit_timestamp_buffers, transaction_buffers,
subtransaction_buffers use 0 to mean auto-tuning based on
shared-buffer size. I think it's worth adding an extra_desc such as "0
to automatically determine this value based on the shared buffer
size".

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center