| From: | Andreas Joseph Krogh <andreas(at)visena(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Incremental backup |
| Date: | 2021-10-28 22:07:11 |
| Message-ID: | VisenaEmail.61.196cd4fcb0034e5c.17cc8ec9428@tc7-visena |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
På torsdag 28. oktober 2021 kl. 23:09:19, skrev Ron <ronljohnsonjr(at)gmail(dot)com
<mailto:ronljohnsonjr(at)gmail(dot)com>>:
[...]
It's still a bunch of transaction logs, whereas differential and incremental
backups only backup the changed pages, no matter how many times they've been
changed.
That's a serious reduction in disk space, and time to apply them.
I think everybody agrees that incremental backup per database, and not
cluster-wide, is nice, and it would be nice if PG supported it. But, given the
way PG is architectured, having cluster-wide WALs, that's not an easy task to
implement.
Repeating "other databases have it" doesn't change that.
--
Andreas Joseph Krogh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2021-10-28 22:24:55 | Re: Incremental backup |
| Previous Message | Hilbert, Karin | 2021-10-28 21:26:39 | Re: How to Resolve Data Being Truncated or Rounded Up During PostgreSQL Migration from v9.623 to v12.8? |