Re: Tracking wait event for latches - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Tracking wait event for latches
Date
Msg-id CA+Tgmobk=Om=bkeuhN-e5DCsU8OcF0EzyOvnptcKmdkq6=utRw@mail.gmail.com
Whole thread Raw
In response to Re: Tracking wait event for latches  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Wed, Sep 21, 2016 at 10:23 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Wed, Sep 21, 2016 at 11:18 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> No, that's not what I want to do.  I think we should categorize the
>> events administratively by their main purpose, rather than
>> technologically by what we're waiting for.
>
> So we'd just have three class IDs instead of one? Well why not.

Yeah, or, I mean, it doesn't have to be three precisely, but I'd like
to try to avoid exposing the users to the fact that we have an
internal data structure called a WaitEventSet and instead classify by
function.

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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Tracking wait event for latches
Next
From: Peter Eisentraut
Date:
Subject: Re: increasing the default WAL segment size