| From: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
|---|---|
| To: | Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Lukas Fittl <lukas(at)fittl(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com> |
| Subject: | Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?) |
| Date: | 2023-01-16 21:41:49 |
| Message-ID: | CAOtHd0AOnW=Cz3XZM7bE2kjyyBhworCoiRMP4kZhru8u_gdN_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 13, 2023 at 10:38 AM Melanie Plageman
<melanieplageman(at)gmail(dot)com> wrote:
>
> Attached is v47.
I missed a couple of versions, but I think the docs are clearer now.
I'm torn on losing some of the detail, but overall I do think it's a
good trade-off. Moving some details out to after the table does keep
the bulk of the view documentation more readable, and the "inform
database tuning" part is great. I really like the idea of a separate
Interpreting Statistics section, but for now this works.
>+ <literal>vacuum</literal>: I/O operations performed outside of shared
>+ buffers while vacuuming and analyzing permanent relations.
Why only permanent relations? Are temporary relations treated
differently? I imagine if someone has a temp-table-heavy workload that
requires regularly vacuuming and analyzing those relations, this point
may be confusing without some additional explanation.
Other than that, this looks great.
Thanks,
Maciek
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2023-01-16 21:42:57 | Re: Perform streaming logical transactions by background workers and parallel apply |
| Previous Message | Andres Freund | 2023-01-16 21:39:13 | "Measuring timing overhead" in docs seems misleading |