Re: Standby server won't start

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Rajeev rastogi" <rajeev(dot)rastogi(at)huawei(dot)com>, "Tatsuo Ishii" <ishii(at)postgresql(dot)org>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Standby server won't start
Date: 2014-03-21 12:07:42
Message-ID: 70934E0D08FD4CF8A9FEBB7C19080E84@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: "Rajeev rastogi" <rajeev(dot)rastogi(at)huawei(dot)com>
If you changed max_connection to 4 only in primary, then I am not able to
understand, how it got changed in standby also (if you have not taken back
again)?
Let me know If I have missed something.

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.

Regards
MauMau

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2014-03-21 12:28:20 Re: Standby server won't start
Previous Message MauMau 2014-03-21 11:54:52 Re: [RFC] What should we do for reliable WAL archiving?