| From: | Francisco Olarte <folarte(at)peoplecall(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 16:47:18 |
| Message-ID: | CA+bJJbwcfkn3w_Nt50oijOOpAXUFqgna6VfvMkRkr4UBMktFtg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 19, 2018 at 8:48 PM, Edmundo Robles <edmundo(at)sw-argos(dot)com> 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.
Replication will happily replicate a delete with no where. Backup will
at least have the day starting point.
For this kind of things you need to do log-archiving + base backups.
With this you can use PITR to roll forward from the last full backup
to just before the delete.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | W. Trevor King | 2018-04-20 18:13:47 | Re: Dynamically filtering a CTE? |
| Previous Message | James Keener | 2018-04-20 16:45:00 | Re: Postgresql database encryption |