Thanks for the comments!
On Wed, Jul 2, 2025 at 7:12 PM Fujii Masao wrote:
> WAL files that have already been replayed can still be read again
> for WAL archiving (if archive_mode = always) or for replication
> (if the standby is acting as a streaming replication sender or
> a logical replication
On 2025/07/02 22:24, Fujii Masao wrote:
On 2025/07/02 19:10, Anthonin Bonnefoy wrote:
Hi,
I've been looking at page cache usage as some of our replicas were
under memory pressure (no inactive pages available) which led to WAL
replay lag as the recovery process had to read from disk. One th
On 2025/07/02 19:10, Anthonin Bonnefoy wrote:
Hi,
I've been looking at page cache usage as some of our replicas were
under memory pressure (no inactive pages available) which led to WAL
replay lag as the recovery process had to read from disk. One thing
I've noticed was that the last WAL file
Hi,
I've been looking at page cache usage as some of our replicas were
under memory pressure (no inactive pages available) which led to WAL
replay lag as the recovery process had to read from disk. One thing
I've noticed was that the last WAL files are in the pagecache even
after having been repla
