Re: Question about Lockhart's book - Mailing list pgsql-hackers

From Christian Convey
Subject Re: Question about Lockhart's book
Date
Msg-id CAPfS4ZyfZ6ibXrL2_cNTehPga7hRtJKXhQ5E7G0GqprirX1Y-A@mail.gmail.com
Whole thread
In response to Re: Question about Lockhart's book  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Thanks very much Josh.  Those sound like great ideas - I'll try to give them a shot. 


On Fri, Dec 27, 2013 at 1:52 PM, Josh Berkus <josh@agliodbs.com> wrote:
On 12/27/2013 08:14 AM, Christian Convey wrote:
> Hi Andrew,
>
> Thanks for your response.  Sometimes overall software architectures stay
> (mostly) unchanged for a long time, and so I figured that's possibly the
> case for Postgresql as well.  But I didn't know, which is why I asked.

Some things in that book will still be accurate and informative.  The
problem is that you, as a beginner, won't know which things are still
good and which are obsolete.

I'd suggest:

- Developer documentation in our primary docs
- Developer FAQ on the wiki
- Bruce's presentations on various internals
- Tom's presentations on how the query planner works
- Various other people's presentations on other aspects, such as foreign
data wrappers, event triggers, etc.

Unfortunately, there's no central index of presentations.

I'm a big fan of "learn by doing", and here's a program which would
bring you up on a LOT of PostgreSQL:

1. Write a few of your own C functions, including trigger functions and
an operator.

2. Write your own foreign data wrapper for something.

3. Write your own Type, including input/output functions, stats
estimation and custom indexing.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Upgrade to Autoconf 2.69
Next
From: Kevin Grittner
Date:
Subject: Re: [BUGFIX] Typos when using the memcmp() function.