Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: x4mmm(at)yandex-team(dot)ru, dilipbalaut(at)gmail(dot)com, tndrwang(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org, tomas(dot)vondra(at)enterprisedb(dot)com
Subject: Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock
Date: 2024-02-29 10:46:42
Message-ID: 202402291046.xpykltdowf22@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2024-Feb-29, Kyotaro Horiguchi wrote:

> At Tue, 27 Feb 2024 18:33:18 +0100, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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".

How about this?

Álvaro Herrera Breisgau, Deutschland —
"La victoria es para quien se atreve a estar solo"

Attachment Content-Type Size
0001-extra_desc.patch text/x-diff 2.0 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-02-29 11:17:29 Re: Synchronizing slots from primary to standby
Previous Message Alvaro Herrera 2024-02-29 10:35:21 Re: Support a wildcard in backtrace_functions