From: | Stefan Fercot <stefan(dot)fercot(at)dalibo(dot)com> |
---|---|
To: | Edmundo Robles <edmundo(at)sw-argos(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Doubts about replication.. |
Date: | 2018-04-20 08:40:14 |
Message-ID: | f4a38417-dd3d-e621-79ff-bb6fe5e77d46@dalibo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
If you want to reduce the amount of data lost, you might want to
consider another type of backup :
https://www.postgresql.org/docs/current/static/continuous-archiving.html
That awsome tool can also help you with it : https://pgbackrest.org/
On 04/19/2018 08:48 PM, Edmundo Robles wrote:
> Yes, you are right, the replication is not a backup ;) , actually
> i backup database daily at 3:00 am but if database crash, the
> amount of data is big! that is the reason i want to replicate to
> reduce the data loss. By the way a few days ago a job partner did a
> delete with no where.
>
> On Thu, Apr 19, 2018 at 1:33 PM, Andreas Kretschmer
> <andreas(at)a-kretschmer(dot)de <mailto:andreas(at)a-kretschmer(dot)de>> wrote:
>
>
>
> Am 19.04.2018 um 19:57 schrieb Edmundo Robles:
>
> I will use replication as simple backup.
>
>
> please keep in mind, replication is not a backup. All logical
> errors on the master (delete from table and forgot the
> where-condition) will replicated to the standby.
>
>
> Andreas
>
> --
> 2ndQuadrant - The PostgreSQL Support Company.
> www.2ndQuadrant.com <http://www.2ndQuadrant.com>
>
>
>
>
>
> --
>
Kind regards,
--
Stefan FERCOT
http://dalibo.com - http://dalibo.org
From | Date | Subject | |
---|---|---|---|
Next Message | Akshay Ballarpure | 2018-04-20 09:24:30 | Re: pg_upgrade help |
Previous Message | PegoraroF10 | 2018-04-20 01:49:54 | Re: Problem with trigger makes Detail record be invalid |