Re: pgsql: Add wait event for fsync of WAL segments

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Add wait event for fsync of WAL segments
Date: 2018-07-08 20:23:37
Message-ID: CAOBaU_bU0caFx-_7+HCDd3CAyznwngpMCwd4ygsDr2RY-CJjOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Hi Michael,

On Mon, Jul 2, 2018 at 3:23 PM, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Add wait event for fsync of WAL segments
>
> Modified Files
> --------------
> doc/src/sgml/monitoring.sgml | 4 ++++

I just noticed that the number of rows for the IO wait event type
documentation hasn't been updated, see
https://www.postgresql.org/docs/devel/static/monitoring-stats.html#WAIT-EVENT-TABLE.

Trivial patch attached.

Attachment Content-Type Size
fix-wait-events-table.diff text/x-patch 654 bytes

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jeff Davis 2018-07-08 23:54:21 pgsql: Fix WITH CHECK OPTION on views referencing postgres_fdw tables.
Previous Message Peter Geoghegan 2018-07-08 17:51:35 pgsql: Correct obsolete unique index insertion comment.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-07-08 21:59:07 Re: cost_sort() improvements
Previous Message Markus Winand 2018-07-08 19:15:42 Re: XML/XPath issues: text/CDATA in XMLTABLE, XPath evaluated with wrong context