Thread: Documentation issue with pg_stat_recovery_prefetch

On Tue, Apr 12, 2022 at 8:11 AM sirisha chamarthi
<sirichamarthi22@gmail.com> wrote:
> I was going through pg_stat_recovery_prefetch documentation and saw an issue with formatting. Attached a small patch
tofix the issue. This is the first time I am sending an email to hackers. Please educate me if I miss something.
 

Thanks Sirisha!

Ouch, that's embarrassing.  My best guess is that I might have screwed
that up a long time ago while rebasing an early development version
over commit 92f94686, which changed the link style and moved
paragraphs around, and then never noticed that it was wrong.
Researching that made me notice another problem: the table was using
the 3 column layout from a couple of years ago, because I had also
missed the style change in commit a0427506.  Oops.  Fixed.

Hi, 

Thank you for developing the new feature.
The pg_stat_recovery_prefetch view documentation doesn't seem to have a description of the stats_reset column. The
attachedsmall patch adds a description of the stats_reset column.
 

Regards,
Noriyoshi Shinoda

-----Original Message-----
From: Thomas Munro <thomas.munro@gmail.com> 
Sent: Tuesday, April 12, 2022 6:23 PM
To: sirisha chamarthi <sirichamarthi22@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Documentation issue with pg_stat_recovery_prefetch

On Tue, Apr 12, 2022 at 8:11 AM sirisha chamarthi <sirichamarthi22@gmail.com> wrote:
> I was going through pg_stat_recovery_prefetch documentation and saw an issue with formatting. Attached a small patch
tofix the issue. This is the first time I am sending an email to hackers. Please educate me if I miss something.
 

Thanks Sirisha!

Ouch, that's embarrassing.  My best guess is that I might have screwed that up a long time ago while rebasing an early
developmentversion over commit 92f94686, which changed the link style and moved paragraphs around, and then never
noticedthat it was wrong.
 
Researching that made me notice another problem: the table was using the 3 column layout from a couple of years ago,
becauseI had also missed the style change in commit a0427506.  Oops.  Fixed.