On Tue, Aug 8, 2017 at 8:11 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Robert Haas wrote: >> On Mon, Aug 7, 2017 at 8:14 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> >> wrote: >> > BTW, I noticed that the PG_WAIT_LOCK value that we're using for wait >> > event here (and in the replication slot case) is bogus. We probably >> > need something new here. >> >> Yeah, if you're adding a new wait point, you should add document a new >> constant in the appropriate section, probably something under >> PG_WAIT_IPC in this case. > > Here's a patch. It turned to be a bit larger than I initially expected.
Álvaro, 030273b7 did not get things completely right. A couple of wait events have been added in the docs for sections Client, IPC and Activity but it forgot to update the counters for morerows . Attached is a patch to fix all that. -- Michael
Description: Binary data
-- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers