[PERFORM] Unable to start the slave instance - Mailing list pgsql-performance

From Daulat Ram
Subject [PERFORM] Unable to start the slave instance
Date
Msg-id 0da1c0fce4504efc9f0681ad94921eb1@cyient.com
Whole thread Raw
List pgsql-performance

Hi experts,

We have configured a replication environment in Windows 10. But I am getting an error below the error messages while starting slave instance.

 

Error:

 

2017-07-05 00:00:02 IST LOG:  restored log file "000000010000000000000022" from archive

2017-07-05 00:00:02 IST LOG:  WAL file is from different database system: WAL file database system identifier is 6438799484563175092, pg_control database system identifier is 6379088242155134709.

2017-07-05 00:00:02 IST FATAL:  database system identifier differs between the primary and standby

2017-07-05 00:00:02 IST DETAIL:  The primary's identifier is 6438799484563175092, the standby's identifier is 6379088242155134709.

2017-07-05 00:00:06 IST LOG:  restored log file "000000010000000000000022" from archive

2017-07-05 00:00:06 IST LOG:  WAL file is from different database system: WAL file database system identifier is 6438799484563175092, pg_control database system identifier is 6379088242155134709.

2017-07-05 00:00:06 IST FATAL:  database system identifier differs between the primary and standby

2017-07-05 00:00:06 IST DETAIL:  The primary's identifier is 6438799484563175092, the standby's identifier is 6379088242155134709.

2017-07-05 00:00:11 IST LOG:  restored log file "000000010000000000000022" from archive

2017-07-05 00:00:11 IST LOG:  WAL file is from different database system: WAL file database system identifier is 6438799484563175092, pg_control database system identifier is 6379088242155134709.

2017-07-05 00:00:11 IST FATAL:  database system identifier differs between the primary and standby

2017-07-05 00:00:11 IST DETAIL:  The primary's identifier is 6438799484563175092, the standby's identifier is 6379088242155134709.

2017-07-05 00:00:16 IST LOG:  restored log file "000000010000000000000022" from archive

2017-07-05 00:00:16 IST LOG:  WAL file is from different database system: WAL file database system identifier is 6438799484563175092, pg

 

 

Below are the parameter at Primary/standby & Recovery.conf as well as hba.conf file.

 

@MASTER

wal_level = hot_standby

shared_buffers = 128MB                                   

port = 5432                                           

max_connections = 100                                                

wal_level = hot_standby                        #                                                         

archive_mode = on                                                                   

archive_command = 'copy "%p" "\\\\192.168.1.111\\archive\\%f"'                                                                                                            

max_wal_senders = 1   

wal_keep_segments = 10

listen_addresses = '*'    

 

@SLAVE

'pgsql-performance@postgresql.org'

 

port = 5432       

hot_standby = on                                 

max_connections = 100                        

listen_addresses = '*'                

shared_buffers = 128MB                                   

                                   

In Recovery.conf

restore_command = 'copy "\\\\192.168.1.111\\archive\\%f" "%p"'

standby_mode = 'on'

primary_coninfo = 'host = 192.168.1.111 port = 5432 user = postgres password = postgres'

 

In Hba.conf @ Master side

# TYPE  DATABASE        USER            ADDRESS                 METHOD

# replication privilege.

host    replication     postgres        192.168.1.106/32        trust

 

Please help on this issue. What things I have to changed & checked.

 

Regards,

Daulat




DISCLAIMER:

This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Check all attachments for viruses before opening them. All views or opinions presented in this e-mail are those of the author and may not reflect the opinion of Cyient or those of our affiliates.

pgsql-performance by date:

Previous
From: Daviramos Roussenq Fortunato
Date:
Subject: Re: [PERFORM] Simple SQL too slow
Next
From: Daulat Ram
Date:
Subject: [PERFORM] Unable to start the slave instance