Re: finding changed blocks using WAL scanning

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: finding changed blocks using WAL scanning
Date: 2019-04-22 23:07:18
Message-ID: 20190422230718.to3fei6dkeppm3zx@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 22, 2019 at 01:15:49PM -0400, Bruce Momjian wrote:
>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.
>

I agree - this would be quite useful for the prefetching use case I've
already mentioned in my previous message.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-04-22 23:07:28 Re: Calling PrepareTempTablespaces in BufFileCreateTemp
Previous Message Tomas Vondra 2019-04-22 23:04:25 Re: finding changed blocks using WAL scanning