From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thomas Reiss <thomas(dot)reiss(at)dalibo(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |
Date: | 2016-03-17 02:03:37 |
Message-ID: | CAB7nPqTJpgAvOK4qSC96Fpm5W+aCtJ9D=3Vn9AfiEYsur=-juw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 16, 2016 at 5:28 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Mar 15, 2016 at 9:17 AM, Thomas Reiss <thomas(dot)reiss(at)dalibo(dot)com> wrote:
>> Here's a small docpatch to fix two typos in the new documentation.
>
> Thanks, committed.
I just had a quick look at the wait_event committed, and I got a
little bit disappointed that we actually do not track latch waits yet,
which is perhaps not that useful actually as long as an event name is
not associated to a given latch wait when calling WaitLatch. I am not
asking for that with this release, this is just for the archive's
sake, and I don't mind coding that myself anyway if need be. The
LWLock tracking facility looks rather cool btw :)
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2016-03-17 02:04:26 | Re: Performance degradation in commit ac1d794 |
Previous Message | Peter Geoghegan | 2016-03-17 01:42:34 | Re: Using quicksort for every external sort run |