Re: [HACKERS] Re: [COMMITTERS] pgsql: Fix inadequacies in recentlyadded wait events
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] Re: [COMMITTERS] pgsql: Fix inadequacies in recentlyadded wait events |
Дата | |
Msg-id | CAB7nPqQOueeu0AFFfojFPGcpGzM5G0gTsz5b6ytB+f=buyyHVg@mail.gmail.com обсуждение исходный текст |
Ответ на | [HACKERS] Re: [COMMITTERS] pgsql: Fix inadequacies in recently added waitevents (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Re: [COMMITTERS] pgsql: Fix inadequacies in recentlyadded wait events
|
Список | pgsql-hackers |
On Tue, Aug 8, 2017 at 11:35 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Thread moved to -hackers. > > Thomas Munro wrote: >> On Wed, Aug 9, 2017 at 7:39 AM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > >> > While at it, fix numerous other problems in the vicinity: > >> All of the above seem like good candidates for a checker script in >> src/tools/check_XXX.pl, a bit like the others I've talked about >> recently [1][2]. > > Yeah, that's one idea, but I think it'd be better to have all these > things be generated content from a single "wait_events.txt" file, like > src/backend/utils/errcodes.txt which gives birth to a whole host of > different files. I would prefer that. Check scripts would tend to be never run. So is there somebody willing to work on that? Or should I as I am responsible to increasing the number of wait events? -- Michael
В списке pgsql-hackers по дате отправления: