| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Replication mode |
| Date: | 2018-01-10 22:44:49 |
| Message-ID: | a9a09d31-4127-2a19-3bc7-085cf442a310@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Azimuddin Mohammed | 2018-01-11 00:08:05 | Re: Replication mode |
| Previous Message | scott ribe | 2018-01-10 22:43:26 | Re: Replication mode |