[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-admin
Subject:    Re: [ADMIN] Changing max_connections after WAL slave configured not allowed?
From:       raghu ram <raghuchennuru () gmail ! com>
Date:       2012-04-13 4:59:43
Message-ID: CALnrrJTU_4pUYhS_QLTMyskMra3NonzNxMz=KYQNih0P4q7wtQ () mail ! gmail ! com
[Download RAW message or body]

On Fri, Apr 13, 2012 at 5:08 AM, Wells Oliver <wellsoliver@gmail.com> wrote:

> I stopped my slave, lowered max_connections to 100 on the primary,
> restarted it, then started the slave back up and it wouldn't go:
>
> 2012-04-12 16:34:32 PDT FATAL:  hot standby is not possible because
> max_connections = 100 is a lower setting than on the master server (its
> value was 200)
>
> Which, OK, it _was_ 200 but now it's definitely 100. Is there a reason
> this change cannot be made now?
>
>
Whenever you modify the configuration parameters in Primary server,those
changes needs to  apply manually in standby server.

If you do not perform changes in standby server,Standby server will
shutdown automatically with above error message.

Please change "max_connection" parameter in postgresql.conf file of standby
server according primary server and then start the Standby server.

-- 

Thanks & Regards,

Raghu Ram

EnterpriseDB: http://www.enterprisedb.com

[Attachment #3 (text/html)]

<br><br><div class="gmail_quote">On Fri, Apr 13, 2012 at 5:08 AM, Wells Oliver <span \
dir="ltr">&lt;<a href="mailto:wellsoliver@gmail.com">wellsoliver@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">

<div>I stopped my slave, lowered max_connections to 100 on the primary, restarted it, \
then started the slave back up and it wouldn&#39;t \
go:</div><div><br></div><div><div>2012-04-12 16:34:32 PDT FATAL:  hot standby is not \
possible because max_connections = 100 is a lower setting than on the master server \
(its value was 200)</div>


</div><div><br></div><div>Which, OK, it _was_ 200 but now it&#39;s definitely 100. Is \
there a reason this change cannot be made now?</div><span class="HOEnZb"><font \
color="#888888"><div><br></div></font></span></blockquote>

<div><br></div><div>Whenever you modify the configuration parameters in Primary \
server,those changes needs to  apply manually in standby server. \
</div><div><br></div><div>If you do not perform changes in standby server,Standby \
server will shutdown automatically with above error message.</div>

<div><br></div><div>Please change &quot;max_connection&quot; parameter in \
postgresql.conf file of standby server according primary server and then start the \
Standby server.</div><div><br></div></div>-- <br>







<p>Thanks &amp; Regards,</p><p>Raghu Ram</p>
<p>EnterpriseDB: <a href="http://www.enterprisedb.com/" \
target="_blank"><span>http://www.enterprisedb.com</span></a></p><br>



[prev in list] [next in list] [prev in thread] [next in thread]