Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
От | Ankit Kumar Pandey |
---|---|
Тема | Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG |
Дата | |
Msg-id | 99a11ec7-fe62-b141-223e-ea6a661bec79@gmail.com обсуждение исходный текст |
Ответ на | Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
|
Список | pgsql-hackers |
> On 11/01/23 09:57, Tom Lane wrote: > IME it's typically a lot more productive to approach things via > "scratch your own itch". If a problem is biting you directly, then > at least you have some clear idea of what it is that needs to be fixed. > You might have to work up to an understanding of how to fix it, but > you have a clear goal. Question is, how newcomers should start contribution if they are not coming with a problem in their hand? Todo list is possibly first thing anyone, who is willing to contribute is going to read and for a new contributor, it is not easy to judge situation (if todo item is easy for newcomers or bit involved). One way to exacerbate this issue is to mention mailing thread with discussions under todo items. It is done for most of todo items but sometime pressing issues are left out. That being said, I think this is part of learning process and okay to come up with ideas and fail. Pghackers can possibly bring up issues in their approach (if discussion for the issue is not mentioned under todo item). -- Regards, Ankit Kumar Pandey
В списке pgsql-hackers по дате отправления: