| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | maumau307(at)gmail(dot)com |
| Cc: | rajeev(dot)rastogi(at)huawei(dot)com, ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Standby server won't start |
| Date: | 2014-03-21 12:28:20 |
| Message-ID: | 20140321.212820.441505741283074347.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> The primary log the new value as an XLOG_PARAMETER_CHANGE WAL record
> at startup when the parameter value in postgresql.conf does not match
> the one in pg_control. Then, the WAL record is sent to the standby
> and applied, which changes the value in pg_control on the standby.
Last time I tested in following way, max_connections in pg_control of
standby did not reflect the change in primary.
1) stop primary
2) stop standby
3) change max_connections to 4 in primary
4) change max_connections to 4 in standby
5) start primary
6) start standby but it failed as I said before
So the particular WAL record was not sent to standby?
I'm going to test again...
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 | MauMau | 2014-03-21 13:04:19 | Re: Standby server won't start |
| Previous Message | MauMau | 2014-03-21 12:07:42 | Re: Standby server won't start |