Thread: Re: [HACKERS] On How To Shorten the Steep Learning Curve Towards PGHacking...
Re: [HACKERS] On How To Shorten the Steep Learning Curve Towards PGHacking...
From
Alvaro Herrera
Date:
Craig Ringer wrote: > Personally I have to agree that the learning curve is very steep. Some > of the docs and presentations help, but there's a LOT to understand. There is a wiki page "Developer_FAQ" which is supposed to help answer these questions. It is currently not very useful, because people stopped adding to it very early and is now mostly unmaintained, but I'm sure it could become a very useful central resource for this kind of information. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Re: [HACKERS] On How To Shorten the Steep Learning Curve Towards PG Hacking...
From
Kang Yuzhe
Date:
Thanks Alvaro for taking your time and pointing me to "Developer_FAQ". I knew this web page and there is good stuff int it.
The most important about "Developer_FAQ" which I believe is that it lists vital books for PG developers.On Mon, Apr 17, 2017 at 8:29 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
Craig Ringer wrote:
> Personally I have to agree that the learning curve is very steep. Some
> of the docs and presentations help, but there's a LOT to understand.
There is a wiki page "Developer_FAQ" which is supposed to help answer
these questions. It is currently not very useful, because people
stopped adding to it very early and is now mostly unmaintained, but
I'm sure it could become a very useful central resource for this kind of
information.
--
Álvaro Herrera https://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Re: [HACKERS] On How To Shorten the Steep Learning Curve Towards PGHacking...
From
Amit Langote
Date:
On 2017/04/18 15:31, Kang Yuzhe wrote: > My question is why is that there is a lot of hands-on about PG application > development(eg. connecting to PG using JAVA/JDBC) but almost nothing about > PG hacking hands-on lessons. For example, I wanna add the keyword > "Encrypted" in CREATE TABLE t1(a int, b int encrypted) or CREATE TABLE t1(a > int, b int) encrypted. Alas, its not easy task. Regarding this part, at one of the links shared above [1], you can find presentations with hands-on instructions about how to implement a new SQL functionality by modifying various parts of the source code. See these: Implementing a TABLESAMPLE clause (by Neil Conway) http://www.neilconway.org/talks/hacking/ottawa/ottawa_slides.pdf Add support for the WHEN clause to the CREATE TRIGGER statement (by Neil Conway) http://www.neilconway.org/talks/hacking/hack_slides.pdf (by Gavin Sherry) https://linux.org.au/conf/2007/att_data/Miniconfs(2f)PostgreSQL/attachments/hacking_intro.pdf Handout: The Implementation of TABLESAMPLE http://www.neilconway.org/talks/hacking/ottawa/ottawa_handout.pdf Handout: Adding WHEN clause to CREATE TRIGGER http://www.neilconway.org/talks/hacking/hack_handout.pdf Some of the details might be dated, because they were written more than 10 years ago, but will definitely get you motivated to dive more into the source code. Thanks, Amit [1] http://www.neilconway.org/talks/hacking/
Re: [HACKERS] On How To Shorten the Steep Learning Curve Towards PG Hacking...
From
Craig Ringer
Date:
On 18 April 2017 at 01:29, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Craig Ringer wrote: > >> Personally I have to agree that the learning curve is very steep. Some >> of the docs and presentations help, but there's a LOT to understand. > > There is a wiki page "Developer_FAQ" which is supposed to help answer > these questions. It is currently not very useful, because people > stopped adding to it very early and is now mostly unmaintained, but > I'm sure it could become a very useful central resource for this kind of > information. I add to it when I think of things. But it'll become an unmaintainable useless morass if random things are just indiscriminately added. Something more structured is needed to cover subsystems, coding rules ("don't LWLockRelease() before ereport(ERROR, ...)"), etc. -- Craig Ringer http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services