| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: finding changed blocks using WAL scanning |
| Date: | 2019-04-22 17:15:49 |
| Message-ID: | 20190422171549.kgaxb3m7stzragjh@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 22, 2019 at 01:11:22PM -0400, Robert Haas wrote:
> On Mon, Apr 22, 2019 at 12:35 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > I assumed the modblock files would be stored in the WAL archive so some
> > external tools could generate incremental backups using just the WAL
> > files. I assumed they would also be sent to standby servers so
> > incremental backups could be done on standby servers too.
>
> Yeah, that's another possible approach. I am not sure what is best.
I am thinking you need to allow any of these, and putting the WAL files
in pg_wal and having them streamed and archived gives that flexibility.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-04-22 17:16:16 | Re: Thoughts on nbtree with logical/varwidth table identifiers, v12 on-disk representation |
| Previous Message | Robert Haas | 2019-04-22 17:11:22 | Re: finding changed blocks using WAL scanning |