| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | zengman <zengman(at)halodbtech(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Minor adjustment: Update the range of the commit_siblings parameter. |
| Date: | 2025-11-10 13:53:52 |
| Message-ID: | 2756C5FD-84BB-4368-AABA-64EBC73F74BA@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Nov 10, 2025, at 19:04, zengman <zengman(at)halodbtech(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2025-11-10 13:57:03 | Re: Trying out <stdatomic.h> |
| Previous Message | Mario González Troncoso | 2025-11-10 13:48:18 | [PATCH} Move instrumentation structs |