| From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Server won't start with fallback setting by initdb. |
| Date: | 2018-02-09 08:08:23 |
| Message-ID: | 20180209.170823.42008365.horiguchi.kyotaro@lab.ntt.co.jp |
| Views: | Whole Thread |Raw Message |Download mbox |Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello.
I'm not sure such a case happens in the real world nowadays,
initdb uses the fallback value of max_connections=10. But it is
out of favor of server since it is not larger than
max_wal_senders(10).
> postgres: max_wal_senders must be less than max_connections
I think that we can safely increase the fallback value to 20 with
which regtests are known not to fail. I believe that is
preferable than explicitly reducing max_wal_senders in the
generated config file. I confirmed that tegtest won't fail with
the value. (Except with permanent failure of dynamic shared
memory)
I don't find documentation about this behavior.
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| increase_min_maxconn_by_initdb_to_20.patch | text/x-patch | 434 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2018-02-09 08:16:35 | Re: [HACKERS] More stats about skipped vacuums |
| Previous Message | Kyotaro HORIGUCHI | 2018-02-09 08:06:35 | Parallel bt build crashes when DSM_NONE |