Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Postgresl Restarting slave problem ?

Pg_log file:
bash-4.2$ tail -f  postgresql-2017-11-08_003645.log
2017-11-08 00:36:45 IST LOG:  database system was interrupted while in recovery at log time 2017-11-08 00:25:54 IST
2017-11-08 00:36:45 IST HINT:  If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target.
2017-11-08 00:36:47 IST FATAL:  the database system is starting up
2017-11-08 00:36:49 IST LOG:  entering standby mode
2017-11-08 00:36:49 IST LOG:  restored log file "00000001000000E400000067" from archive
2017-11-08 00:36:49 IST FATAL:  hot standby is not possible because max_connections = 500 is a lower setting than on the master server (its value was 800)
2017-11-08 00:36:49 IST LOG:  startup process (PID 20428) exited with exit code 1
2017-11-08 00:36:49 IST LOG:  aborting startup due to startup process failure
2017-11-08 00:36:49 IST LOG:  database system is shut down
then i tried starting only it showed postmaster.pid does not exist
After changing slave max_connections from  500 to 800 problem was solved
becouse master and slave  max_connections should be same


Popular posts from this blog

rman interview and scenario based questions and answer and also rman(backup and recovery) discussions panel

How to Get Table Size, Database Size, Indexes Size, schema Size, Tablespace Size, column Size in PostgreSQL Database

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

7 Steps to configure BDR replication in postgresql

PostgreSQL pgBadger