From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Daulat Ram <Daulat(dot)Ram(at)cyient(dot)com> |
Cc: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Unable to start the slave instance |
Date: | 2017-07-06 05:10:00 |
Message-ID: | CAB7nPqS0NrdFpQ9LvnFRrrgpG6AOr_Uivm8E6pc0jCyJqdkPiA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, Jul 6, 2017 at 2:02 PM, Daulat Ram <Daulat(dot)Ram(at)cyient(dot)com> wrote:
> We are using different releases of windows. Is this issue reported due to different versions of windows releases.
> Master server : Windows 7 Professional
> Slave server : Windows 10 Professional
Please do not top-post.
That may be a problem. Versions of PostgreSQL compiled across
different platforms are different things, and replication is not
supported for that as things happen at a low binary level.
> Step:9
> Replicating the Initial database:
> On the master server, we can use an internal postgres backup start command to create a backup label command. We then will transfer the database data to our slave and then issue an internal backup stop command to clean up:
> psql -c “select pg_start_backup(‘initial_backup’);”
> rsync -cva –inplace –exclude=*pg_xlog* /var/lib/postgresql/9.3/main/ slave_IP_address:/var/lib/postgresql/9.3/main/
> psql -c “select pg_stop_backup ();”
Shouldn't you remove the data of the slave as well first?
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Rick Otten | 2017-07-06 15:03:54 | partitioning materialized views |
Previous Message | Daulat Ram | 2017-07-06 05:02:11 | Re: Unable to start the slave instance |