From: | Ankit Kumar Pandey <itsankitkp(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, pghackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG |
Date: | 2023-01-11 06:37:58 |
Message-ID: | 99a11ec7-fe62-b141-223e-ea6a661bec79@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-01-11 06:39:31 | Re: Fix pg_publication_tables to exclude generated columns |
Previous Message | Michael Paquier | 2023-01-11 06:27:12 | Re: Avoiding "wrong tuple length" errors at the end of VACUUM on pg_database update (Backpatch of 947789f to v12 and v13) |