From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | "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: Added PostgreSQL internals learning materials in Developer FAQ |
Date: | 2017-12-11 08:39:39 |
Message-ID: | CAMsr+YETRYSLPDg6++0f7wh+V9RQ0AJ6Jz8=POfi0Nhs=yc0QA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11 December 2017 at 14:50, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Mon, Dec 11, 2017 at 8:43 AM, Tsunakawa, Takayuki
> <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
> > Hello,
> >
> > FYI
> > I collected Web resources to learn PostgreSQL internals in the Developer
> FAQ page. I did this because I need to provide self-education materials
> for new developers. Specifically, I modified "How is the source code
> organized?", and added "What information is available to learn PostgreSQL
> internals?".
> >
> > Developer FAQ
> > https://wiki.postgresql.org/wiki/Developer_FAQ#
> Development_Tools_and_Help
> >
> >
> > I borrowed most of the information from the following discussion.
> >
>
> Thanks, looks like quite useful information for the new people who
> want to learn about PostgreSQL especially internals.
>
>
While we're talking wiki changes, some folks may be interested in the
recent stuff I added to the profiling with perf page
https://wiki.postgresql.org/wiki/Profiling_with_perf on using postgres's
predefined tracepoints, injecting userspace tracepoints, capturing variable
values at tracepoints, etc.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2017-12-11 08:54:24 | Re: [HACKERS] WAL logging problem in 9.4.3? |
Previous Message | Ashutosh Bapat | 2017-12-11 08:39:13 | Re: Out of date comment in cached_plan_cost |