Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\))
Subject: Re: Minor adjustment: Update the range of the commit_siblings
 parameter.
From: Chao Li <li.evan.chao@gmail.com>
In-Reply-To: <tencent_53B70BA72303AE9C6889E78E@qq.com>
Date: Mon, 10 Nov 2025 21:53:52 +0800
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2756C5FD-84BB-4368-AABA-64EBC73F74BA@gmail.com>
References: <tencent_53B70BA72303AE9C6889E78E@qq.com>
To: zengman <zengman@halodbtech.com>
Archived-At: 
 <https://www.postgresql.org/message-id/2756C5FD-84BB-4368-AABA-64EBC73F74BA%40gmail.com>
Precedence: bulk


> On Nov 10, 2025, at 19:04, zengman <zengman@halodbtech.com> wrote:
>=20
> Hi, hackers
>=20
> 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.
>=20
> --=20
> 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 =3D> 'commit_siblings', type =3D> 'int', context =3D> =
'PGC_USERSET', group =3D> 'WAL_SETTINGS',
  short_desc =3D> 'Sets the minimum number of concurrent open =
transactions required before performing "commit_delay".',
  variable =3D> 'CommitSiblings',
  boot_val =3D> '5',
  min =3D> '0',
  max =3D> '1000',
},
```

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/