Thanks mark..
That does help...
Our db is not transactional ..it more of write few times read many times ..What HA do you recommend for us by not using any open source tools...and what could be the best backup startegy...
Appreciate your response.
On Jan 10, 2018 4:44 PM, "Mark Kirkwood" <mark.kirkwood@xxxxxxxxxxxxxxx> wrote:
On 11/01/18 11:17, Azimuddin Mohammed wrote:
Thanks!
But with hot standby my slave will be in read-only mode ...how can I just use my slave as a backup and not do any read operation and let my primary server do all read and write operation. If my primary fails I will do manual failover. The whole idea is to remove any 3rd party open source tools as we are not sure how well they behave and avoid any single point of failure.
Whether you have made the standby/slave hot or merely warm doesn't really change the 'standby' part - the mechanism is identical (applying wal information to keep the it up to date with its primary). In either case they cannot be altered by clients (attempting to) connect to them. So most folk always make their standbys 'hot' (it is very convenient to have the *option* of being able to query them if you need to).
Does that help?
Cheers
Mark
