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

From Michael Paquier
Subject Re: finding changed blocks using WAL scanning
Date
Msg-id 20190416034535.GC2673@paquier.xyz
Whole thread Raw
In response to Re: finding changed blocks using WAL scanning  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: finding changed blocks using WAL scanning
List pgsql-hackers
On Mon, Apr 15, 2019 at 09:04:13PM -0400, Robert Haas wrote:
> That is pretty much exactly what I was intending to propose.

Any caller of XLogWrite() could switch to a new segment once the
current one is done, and I am not sure that we would want some random
backend to potentially slow down to do that kind of operation.

Or would a separate background worker do this work by itself?  An
external tool can do that easily already:
https://github.com/michaelpq/pg_plugins/tree/master/pg_wal_blocks
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: ExecForceStoreMinimalTuple leaks memory like there's no tomorrow
Next
From: Michael Paquier
Date:
Subject: Re: New vacuum option to do only freezing