From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: max_connections and standby server |
Date: | 2015-08-11 05:47:18 |
Message-ID: | 20150811.144718.2305257792591832660.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Somebody refresh my memory as to why we have this restriction (that is,
> slave's max_connections >= master's max_connections) in the first place?
> Seems like it should not be a necessary requirement, and working towards
> getting rid of it would be far better than any other answer.
If you care about max_connections, you might want to care about below as well (from xlog.c)
RecoveryRequiresIntParameter("max_worker_processes",
max_worker_processes,
ControlFile->max_worker_processes);
RecoveryRequiresIntParameter("max_prepared_transactions",
max_prepared_xacts,
ControlFile->max_prepared_xacts);
RecoveryRequiresIntParameter("max_locks_per_transaction",
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2015-08-11 05:53:59 | Re: [PROPOSAL] VACUUM Progress Checker. |
Previous Message | Tom Lane | 2015-08-11 05:42:48 | Re: max_connections and standby server |