Re: On How To Shorten the Steep Learning Curve Towards PG Hacking...

Hello Simon,
The journey that caused and is causing me a lot of pain is finding my way
in PG development.
Complex Code Reading like PG. Fully understanding the science of DBMS
Engines: Query Processing, Storage stuff, Transaction Management and so
on...

Anyway as you said, the rough estimation towards any expertise seems to be
in abidance with by The 10,000 Hour Rule. I will strive based on this rule.

For now, would please tell me how to know the exact PG version to which a
specific patch was developed?
Given x patch, how do I know the specific PG version it was developed for?

Regards,
Zeray

On Mon, Apr 17, 2017 at 7:33 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> On 27 March 2017 at 13:00, Kang Yuzhe <tiggreen87(at)gmail(dot)com> wrote:
>
> > I have found PG source Code reading and hacking to be one the most
> > frustrating experiences in my life. I believe that PG hacking should
> not be
> > a painful journey but an enjoyable one!
> >
> > It is my strong believe that out of my PG hacking frustrations, there may
> > come insights for the PG experts on ways how to devise hands-on with PG
> > internals so that new comers will be great coders as quickly as possible.
>
> I'm here now because PostgreSQL has clear, well designed and
> maintained code with accurate docs, great comments and a helpful team.
>
> I'd love to see detailed cases where another project is better in a
> measurable way; I am willing to learn from that.
>
> Any journey to expertise takes 10,000 hours. There is no way to shorten
> that.
>
> What aspect of your journey caused you pain?
>
> --
> Simon Riggs http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>