overy has begun. >> Recovery has not begun. Without the change, the recovery will not start. So, >do I have to do a reload, or restart, for the parameter to take effect? The >situation is - master is up and running, slave is up and running. I made a >change to recovery.conf. How can I make slave 'accept' that change? >I think that you are mixing things here. recovery.conf is read once at server >start up and its presence puts the server in archive recovery. >Check the output of "SELECT pg_is_in_recovery()" and you will see that its >output is true, meaning that the node is in recovery. On the other hand, >trigger_file is used for a node promotion, making the node exit the archive >recovery mode and turn it into a master node. So to make the new parameter >have effect restart the server. >-- As you said, I was mixing things there. When you said recovery has begun, I confused it with promotion. Apologies. I tried restarting the standby node and it worked. Thanks a lot, Jayadevan DISCLAIMER: "The information in this e-mail and any attachment is intended only for the person to whom it is addressed and may contain confidential and/or privileged material. If you have received this e-mail in error, kindly contact the sender and destroy all copies of the original communication. IBS makes no warranty, express or implied, nor guarantees the accuracy, adequacy or completeness of the information contained in this email or any attachment and is not liable for any errors, defects, omissions, viruses or for resultant loss or damage, if any, direct or indirect." -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
