From: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com> |
---|---|
To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
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:17:41 |
Message-ID: | CAKUuFd72Daabtt4Hyyd7Nr_vUEVkN82Q8wJpdCkCBwC63ZS4yQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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.
On Jan 10, 2018 4:11 PM, "Mark Kirkwood" <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
wrote:
> On 11/01/18 11:00, Peter Eisentraut wrote:
>
> On 1/10/18 15:24, Azimuddin Mohammed wrote:
>>
>>> May I know what is the core difference between HOT standby. Warm Stand
>>> by ?
>>>
>> In PostgreSQL, "hot standby" is a mode for an instance in recovery that
>> allows read-only commands to be executed on it. The term "warm standby"
>> is not used by PostgreSQL, but you could think of a server in recovery
>> that does not allow queries to be a warm standby, if you wish.
>>
>>
> We do talk about 'warm standby' in the docs:
>
> https://www.postgresql.org/docs/10/static/warm-standby.html
>
> ...altho we do not precisely say how to setup this up as opposed to the
> 'hot' variant. In fact it is pretty easy to (accidentally) get a warm
> standby by forgetting to set :
>
> standby_mode = 'on'
>
> in recovery.conf
>
> Cheers
>
> Mark
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2018-01-10 22:36:28 | Re: Replication mode |
Previous Message | Mark Kirkwood | 2018-01-10 22:11:38 | Re: Replication mode |