| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Kang Yuzhe <tiggreen87(at)gmail(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: On How To Shorten the Steep Learning Curve Towards PG Hacking... |
| Date: | 2017-04-18 07:50:59 |
| Message-ID: | CAMsr+YG=keBaEk-J4SQmLDkhw8S-2THTG0hHBQsQ6RFDSA3dHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 18 April 2017 at 01:29, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-04-18 07:54:17 | Re: On How To Shorten the Steep Learning Curve Towards PG Hacking... |
| Previous Message | Kang Yuzhe | 2017-04-18 07:41:21 | Re: On How To Shorten the Steep Learning Curve Towards PG Hacking... |