Re: Contribution to PostgreSQL - please give an advice - Mailing list pgsql-hackers

From Ian Zagorskikh
Subject Re: Contribution to PostgreSQL - please give an advice
Date
Msg-id CAHNuAPFnXcfb7O8-=iivTJ-=Reo9wGCdGC3tNwH-hpufN+jQ=w@mail.gmail.com
Whole thread Raw
In response to Re: Contribution to PostgreSQL - please give an advice  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
All,

Guys, thank you all for your advice! As a starting point I definitely should take a look at the current Commitfest and try to help in review as best I can. Thanks!

Regards,



пн, 12 апр. 2021 г. в 16:38, Justin Pryzby <pryzby@telsasoft.com>:
On Mon, Apr 12, 2021 at 03:21:41PM +0000, Ian Zagorskikh wrote:
> I would like to contribute my time and efforts to the PostgreSQL project
> development. I have some [hope not too bad] experience in software
> development primarily for Linux/BSD/Windows platforms with C/C++ though
> almost no experience in RDBMS internals. I have read the "Development
> Information" section in wiki and checked the official TODO list. It's
> really great but it's a bit huge and "all is so tasty" so I don't know
> where to start. Can you please advise me how to proceed? Maybe there are
> active tasks or bugs or issues that require man power? I would appreciate
> any advice or mentorship. Thank you!

I think the best way is to start following this mailing list.
Since it's very "busy", it may be easier to follow the web archives.
https://www.postgresql.org/list/pgsql-hackers/2021-04/

When someone reports a problem, you can try to reproduce it to see if they've
provided enough information to confirm the issue, or test any proposed patch.

You can see the patches being proposed for future release:
https://commitfest.postgresql.org/

However, right now, we've just passed the "feature freeze" for v14, so new
development is on hold for awhile.  What's most useful is probably testing the
changes that have been committed.  You can check that everything works as
described, that the implemented behavior doesn't have any rough edges, that the
features work together well, and work under your own use-cases/workloads.

You can see a list of commits for v14 like so:
> git log --cherry-pick origin/REL_13_STABLE...origin/master
(Any commits that show up twice are also in v13, so aren't actually "new in
v14", but the patches differ so GIT couldn't figure that out)

--
Justin


--
Best Regards,
Ian Zagorskikh

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: New IndexAM API controlling index vacuum strategies
Next
From: Fujii Masao
Date:
Subject: Re: TRUNCATE on foreign table