From: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com> |
---|---|
To: | Ankit Kumar Pandey <itsankitkp(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 08:22:57 |
Message-ID: | CAFBsxsEYSF7FTqN5=ko=S257OaCoU9wWz_1p70F2K2ovpMKoTA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 11, 2023 at 1:38 PM Ankit Kumar Pandey <itsankitkp(at)gmail(dot)com>
wrote:
>
>
> > 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?
I would say find something that gets you excited. Worked for me, at least.
> Todo list is possibly first thing anyone, who is willing to contribute
> is going to read and for a new
Yeah, that's a problem we need to address.
> That being said, I think this is part of learning process and okay to
> come up with ideas and fail.
Of course it is! A key skill in engineering is to fail as quickly as
possible, preferably before doing any actual work.
--
John Naylor
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Melih Mutlu | 2023-01-11 08:31:12 | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |
Previous Message | Michael Paquier | 2023-01-11 07:53:39 | Re: recovery modules |