Re: Tracking wait event for latches
От | Michael Paquier |
---|---|
Тема | Re: Tracking wait event for latches |
Дата | |
Msg-id | CAB7nPqRFg878JQHWcDUzHBstHat4zWMbd8EEJ=w3n=4HWrygjg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Tracking wait event for latches (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Tracking wait event for latches
|
Список | pgsql-hackers |
On Wed, Sep 28, 2016 at 9:35 PM, Robert Haas <robertmhaas@gmail.com> wrote: > On Tue, Sep 27, 2016 at 8:39 PM, Thomas Munro > <thomas.munro@enterprisedb.com> wrote: >> Ok, if they really are independent then shouldn't we take advantage of >> that at call sites where we might be idle but we might also be waiting >> for the network? > > I certainly didn't intend for them to be independent, and I don't > think they should be. I think it should be a hierarchy - as it is > currently. I think it's a bad idea to introduce the notational > overhead of having to pass through two integers rather than one > everywhere, and a worse idea to encourage people to think of the > wait_event_type and wait_event are related any way other than > hierarchically. So should I change back the patch to have only one argument for the eventId, and guess classId from it? -- Michael
В списке pgsql-hackers по дате отправления: