Re: Re: [COMMITTERS] pgsql: Fix inadequacies in recently added wait events

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Fetter <david(at)fetter(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Fix inadequacies in recently added wait events
Date: 2017-08-09 19:25:56
Message-ID: 20170809192556.koklj3dremkc5bfb@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:

> I think generating whatever we can from a single authoritative file
> is indeed a good idea.

Yay.

> But I had the impression that people also wanted to enforce a rule
> about "only one use of each wait event name", which'd require a
> checker script, no? (I'm not really convinced that we need such a
> rule, fwiw.)

I'm not convinced of that, either. Of the possible problems in the
area, that seems the lesser one.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-08-09 21:03:51 pgsql: Fix handling of container types in find_composite_type_dependenc
Previous Message Tom Lane 2017-08-09 17:35:33 Re: Re: [COMMITTERS] pgsql: Fix inadequacies in recently added wait events

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-08-09 19:29:04 Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values
Previous Message Dean Rasheed 2017-08-09 18:56:12 Re: dubious error message from partition.c