From: Chao Li <li.evan.chao@gmail.com>
To: zengman <zengman@halodbtech.com>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Minor adjustment: Update the range of the commit_siblings parameter.
Date: Mon, 10 Nov 2025 21:53:52 +0800
Message-ID: <2756C5FD-84BB-4368-AABA-64EBC73F74BA@gmail.com> (raw)
In-Reply-To: <tencent_53B70BA72303AE9C6889E78E@qq.com>
References: <tencent_53B70BA72303AE9C6889E78E@qq.com>
> On Nov 10, 2025, at 19:04, zengman <zengman@halodbtech.com> wrote:
>
> Hi, hackers
>
> When reviewing the postgresql.conf.sample file, I noticed that the range of the commit_siblings parameter appears to have been incorrect for quite some time. Attached is a simple patch to update it.
>
> --
> Regrads,
> Man Zeng<001_update_postgresql_conf_sample.patch>
Yes, the definition in guc_parameters.dat shows min as 0 and max as 1000, so the fix is correct:
```
{ name => 'commit_siblings', type => 'int', context => 'PGC_USERSET', group => 'WAL_SETTINGS',
short_desc => 'Sets the minimum number of concurrent open transactions required before performing "commit_delay".',
variable => 'CommitSiblings',
boot_val => '5',
min => '0',
max => '1000',
},
```
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: li.evan.chao@gmail.com, zengman@halodbtech.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Minor adjustment: Update the range of the commit_siblings parameter.
In-Reply-To: <2756C5FD-84BB-4368-AABA-64EBC73F74BA@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox