Re: wait events for disk I/O

From: Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Rahila Syed <rahilasyed90(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: wait events for disk I/O
Date: 2017-03-18 17:22:43
Message-ID: CAGPqQf1Xhf5CjZH1XJNB+AY-_So3f4V_Tk_eqRwdRwhiX1JcRg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 18, 2017 at 5:15 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> On Fri, Mar 17, 2017 at 10:01 AM, Rushabh Lathia
> <rushabh(dot)lathia(at)gmail(dot)com> wrote:
> > I tried to cover all the suggestion in the attached latest patch.
>
> Committed. I reworded the documentation entries, renamed a few of the
> wait events to make things more consistent, put all three lists in
> rigorous alphabetical order, and I fixed a couple of places where an
> error return from a system call could lead to returning without
> clearing the wait event.
>
>
Thanks Robert.

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

--
Rushabh Lathia

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mithun Cy 2017-03-18 17:29:21 Re: [POC] A better way to expand hash indexes.
Previous Message Stephen Frost 2017-03-18 17:18:53 pgsql: Improve pg_dump regression tests and code coverage