From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Luca Ferrari <fluca1978(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: max_connections different between primary and standby: is it possible? |
Date: | 2022-02-03 14:55:09 |
Message-ID: | 252827.1643900109@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> On Thu, Feb 03, 2022 at 05:39:57PM +0530, Bharath Rupireddy wrote:
>> ... Instead, it would be better
>> if the server emits a single log with all the insufficient
>> parameters(max_connections, max_worker_processes, max_wal_senders,
>> max_prepared_transactions and max_locks_per_transaction) values and
>> crashes FATALly. The users can look at the logs at once, set all the
> Sure, but one failed start / inspect logs / modify configuration / start will
> always by longer than just reading the docs and making sure that the
> configuration is appropriate. It also won't help if you want to modify the
> settings on your primary and make sure that you won't have an incident on your
> HA setup.
I don't recall any field complaints, ever, about this behavior.
So I'm skeptical that it's a place to expend effort.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-02-03 15:00:37 | Re: sort order for UTF-8 char column with Japanese UTF-8 |
Previous Message | Rama Krishnan | 2022-02-03 14:54:10 | Oracle to postgresql migration |