Re: Refactor documentation for wait events (Was: pgsql: Add waitevent for fsync of WAL segments) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Refactor documentation for wait events (Was: pgsql: Add waitevent for fsync of WAL segments)
Date
Msg-id CA+TgmoYPJiG5dez-LiBW_9jxte98Czep0Em39NK6nWx-M4zrhg@mail.gmail.com
Whole thread Raw
In response to Refactor documentation for wait events (Was: pgsql: Add wait eventfor fsync of WAL segments)  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Refactor documentation for wait events (Was: pgsql: Add waitevent for fsync of WAL segments)  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Sun, Jul 15, 2018 at 10:10 PM, Michael Paquier <michael@paquier.xyz> wrote:
> On Fri, Jul 13, 2018 at 04:57:59PM -0500, Robert Haas wrote:
>> On Mon, Jul 9, 2018 at 4:41 PM, Michael Paquier <michael@paquier.xyz> wrote:
>>> Another idea that I have here, is to rework the page for monitoring
>>> stats so as we create one sub-section for each system view, and also one
>>> for the table of wait events.  For the wait events, we could then
>>> completely remove the first category column which has morerows and
>>> divide the section into on table per event category.
>>
>> +1 from me.  I think I proposed that before.
>
> Attached is a proof of concept of that.  I have divided the "Viewing
> Statistics" section into a subset for each catalog, and each wait event
> type gains its sub-section as well.  There is a bit more to do with the
> indentation and some xreflabels, but I think that this is enough to
> begin a discussion.
>
> Thoughts?

This doesn't seem to get rid of the morerows stuff.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Next
From: Jeremy Finzel
Date:
Subject: Re: Logical decoding from promoted standby with same replication slot