From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Our naming of wait events is a disaster.
Date: Tue, 12 May 2020 16:54:39 -0400
Message-ID: <6405.1589316879@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmoZJoqNmgv0U2S5bcqnFaNtaCeesWLZxA+3pvU3aD2bsvA@mail.gmail.com>
References: <21247.1589296570@sss.pgh.pa.us>
<CA+TgmoZJoqNmgv0U2S5bcqnFaNtaCeesWLZxA+3pvU3aD2bsvA@mail.gmail.com>
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, May 12, 2020 at 11:16 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I've been trying to reformat table 27.4 (wait events) to fit
>> into PDF output, which has caused me to study its contents
>> more than I ever had before.
> That reminds me that it might be easier to maintain that table if we
> broke it up into one table per major category - that is, one table for
> lwlocks, one table for IPC, one table for IO, etc. - instead of a
> single table with a row-span number that is large and frequently
> updated incorrectly.
Yeah, see my last attempt at
https://www.postgresql.org/message-id/26961.1589260206%40sss.pgh.pa.us
I'm probably going to go with that, but as given that patch conflicts
with my other pending patch to change the catalog description tables,
so I want to push that other one first and then clean up the wait-
event one. In the meantime, I'm going to look at these naming issues,
which will also be changing that patch ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Our naming of wait events is a disaster.
In-Reply-To: <6405.1589316879@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox