Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG - Mailing list pgsql-hackers

From John Naylor
Subject Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
Date
Msg-id CAFBsxsEYSF7FTqN5=ko=S257OaCoU9wWz_1p70F2K2ovpMKoTA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Improve ability to display optimizer analysis using OPTIMIZER_DEBUG  (Ankit Kumar Pandey <itsankitkp@gmail.com>)
List pgsql-hackers

On Wed, Jan 11, 2023 at 1:38 PM Ankit Kumar Pandey <itsankitkp@gmail.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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: recovery modules
Next
From: Melih Mutlu
Date:
Subject: Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication