Re: Our naming of wait events is a disaster.
От | Tom Lane |
---|---|
Тема | Re: Our naming of wait events is a disaster. |
Дата | |
Msg-id | 6405.1589316879@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Our naming of wait events is a disaster. (Robert Haas <robertmhaas@gmail.com>) |
Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: