| From: | Israel Brewster <ijbrewster(at)alaska(dot)edu> |
|---|---|
| To: | normandavis1990 <normandavis1990(at)proton(dot)me> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: High Availability and Replication |
| Date: | 2024-02-29 20:08:59 |
| Message-ID: | 9AAC605E-884E-44BA-8488-32D58B45D884@alaska.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Feb 29, 2024, at 10:15 AM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>
>
> On Thursday, February 29, 2024, normandavis1990 <normandavis1990(at)proton(dot)me <mailto:normandavis1990(at)proton(dot)me>> wrote:
>>
>> What is the difference between High Availability and Replication?
>
> The former is a goal, the later is a technique.
Perhaps more specifically: Replication is simply Replicating - or copying - the “master” database to one or more “slave” databases, generally in real-time such that the slave database clusters are replicas of the master. This is good when the master goes down, because you’ll still have one or more copies of it available, but by itself it doesn’t keep there from being an outage if/when the master goes down.
High Availability layers on top of replication to provide some means of ensuring that the database is HIGHLY available, such as an automatic failover system or load balancer. Many different options that work in many different ways are available to help meet this goal.
---
Israel Brewster
Software Engineer
Alaska Volcano Observatory
Geophysical Institute - UAF
2156 Koyukuk Drive
Fairbanks AK 99775-7320
Work: 907-474-5172
cell: 907-328-9145
>
> David J.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sud | 2024-02-29 20:29:58 | Re: Question on Table creation |
| Previous Message | Adrian Klaver | 2024-02-29 20:05:25 | Re: High Availability and Replication |