Re: [PERFORM] Unable to start the slave instance
| От | Scott Marlowe |
|---|---|
| Тема | Re: [PERFORM] Unable to start the slave instance |
| Дата | |
| Msg-id | CAOR=d=2Y9Q1PMF6kY3ci6ZdxpVQ+PjEd8gjG0Tdjhax=f-rCvA@mail.gmail.com обсуждение исходный текст |
| Ответ на | [PERFORM] Unable to start the slave instance (Daulat Ram <Daulat.Ram@cyient.com>) |
| Ответы |
Re: [PERFORM] Unable to start the slave instance
|
| Список | pgsql-performance |
On Wed, Jul 5, 2017 at 3:26 AM, Daulat Ram <Daulat.Ram@cyient.com> wrote: > Hi experts, > > We have configured a replication environment in Windows 10. But I am getting > 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. > So how did you get to here? It doesn't look like a proper rsync or pg_basebackup method got you here.
В списке pgsql-performance по дате отправления: