Re: finding changed blocks using WAL scanning - Mailing list pgsql-hackers

From Andres Freund
Subject Re: finding changed blocks using WAL scanning
Date
Msg-id 20190418215238.eeii6znzlr6z7exe@alap3.anarazel.de
Whole thread Raw
In response to Re: finding changed blocks using WAL scanning  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 2019-04-18 17:47:56 -0400, Bruce Momjian wrote:
> I can see a 1GB marker being used for that.  It would prevent an
> incremental backup from being done until the first 1G modblock files was
> written, since until then there is no record of modified blocks, but
> that seems fine.  A 1G marker would allow for consistent behavior
> independent of server restarts and base backups.

That doesn't seem like a good idea - it'd make writing regression tests
for this impractical.



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_dump is broken for partition tablespaces
Next
From: Tom Lane
Date:
Subject: Re: Race conditions with checkpointer and shutdown