Changing max_connections after WAL slave configured not allowed?

From: Wells Oliver <wellsoliver(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Changing max_connections after WAL slave configured not allowed?
Date: 2012-04-12 23:38:13
Message-ID: CAOC+FBXLMfyw5Wz4U+jDUt4yFim5HaPnd3+BgKpfBq9UODDghQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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?

--
Wells Oliver
wellsoliver(at)gmail(dot)com

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message raghu ram 2012-04-13 04:47:43 Re: Changing max_connections after WAL slave configured not allowed?
Previous Message Tom Lane 2012-04-11 23:51:24 Re: Definitive logrotate solution?