Re: WAL usage calculation patch
Julien Rouhaud <rjuju123@gmail.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Change the display of WAL usage statistics in Explain.
- 69bfaf2e1de4 13.0 landed
-
Cosmetic fixups for WAL usage work.
- ef08ca113fe3 13.0 landed
-
Allow parallel create index to accumulate buffer usage stats.
- 5c71362174eb 13.0 landed
- f179e9f01b65 11.8 landed
- 13823ad3b012 12.3 landed
-
Allow autovacuum to log WAL usage statistics.
- b7ce6de93b59 13.0 landed
-
Add the option to report WAL usage in EXPLAIN and auto_explain.
- 33e05f89c53e 13.0 landed
-
Allow pg_stat_statements to track WAL usage statistics.
- 6b466bf5f2be 13.0 landed
-
Add infrastructure to track WAL usage.
- df3b181499b4 13.0 landed
-
Include information on buffer usage during planning phase, in EXPLAIN output, take two.
- ce77abe63cfc 13.0 cited
-
Include information on buffer usage during planning phase, in EXPLAIN output.
- ed7a5095716e 13.0 cited
-
Allow parallel vacuum to accumulate buffer usage.
- 3a5e22138a8d 13.0 landed
-
Allow pg_stat_statements to track planning statistics.
- 17e03282241c 13.0 cited
On Mon, Apr 13, 2020 at 8:11 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Sat, Apr 11, 2020 at 6:55 PM Julien Rouhaud <rjuju123@gmail.com> wrote: > > > > On Fri, Apr 10, 2020 at 9:37 PM Julien Rouhaud <rjuju123@gmail.com> wrote: > > > > > I tried to take into account all that have been discussed, but I have > > to admit that I'm absolutely not sure of what was actually decided > > here. I went with those changes: > > > > - rename wal_num_fpw to wal_fpw for consistency, both in pgss view > > fiel name but also everywhere in the code > > - change comments to consistently mention "full page writes generated" > > - changed pgss and explain documentation to mention "full page images > > generated", from Justin's patch on another thread > > > > I think it is better to use "full page writes" to be consistent with > other places. > > > - kept "amount" of WAL bytes > > > > Okay, but I would like to make another change suggested by Justin > which is to replace "count" with "number" at a few places. Ah sorry I missed this one. +1 it also sounds better. > I have made the above two changes in the attached. Let me know what > you think about attached? It all looks good to me! > > - no change to the explain output as I have no idea what is the > > consensus (one or two spaces, use semicolon or equal, show unit or > > not) > > > > Yeah, let's do this separately once we have consensus. Agreed.