RE: WIP: WAL prefetch (another approach)

Hi,
Thank you for your reply.
I missed the message, sorry.

Regards,
Noriyoshi Shinoda

-----Original Message-----
From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Sent: Tuesday, April 12, 2022 6:28 PM
To: Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi(dot)shinoda(at)hpe(dot)com>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>; Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>; Stephen Frost <sfrost(at)snowman(dot)net>; Andres Freund <andres(at)anarazel(dot)de>; Jakub Wartak <Jakub(dot)Wartak(at)tomtom(dot)com>; Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>; Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>; Dmitry Dolgov <9erthalion6(at)gmail(dot)com>; David Steele <david(at)pgmasters(dot)net>; pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: WAL prefetch (another approach)

On Tue, Apr 12, 2022 at 9:03 PM Shinoda, Noriyoshi (PN Japan FSIP) <noriyoshi(dot)shinoda(at)hpe(dot)com> wrote:
> Thank you for developing the great feature. I tested this feature and checked the documentation. Currently, the documentation for the pg_stat_prefetch_recovery view is included in the description for the pg_stat_subscription view.
>
> INVALID URI REMOVED
> toring-stats.html*MONITORING-PG-STAT-SUBSCRIPTION__;Iw!!NpxR!xRu7zc4Hc
> ZppB-32Fp3YfESPqJ7B4AOP_RF7QuYP-kCWidoiJ5txu9CW8sX61TfwddE$

Hi! Thanks. I had just committed a fix before I saw your message, because there was already another report here:

https://www.postgresql.org/message-id/flat/CAKrAKeVk-LRHMdyT6x_p33eF6dCorM2jed5h_eHdRdv0reSYTA(at)mail(dot)gmail(dot)com