From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | "youngvonlee(at)gmail(dot)com" <youngvonlee(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgresql source code is worth to read |
Date: | 2009-06-05 17:07:13 |
Message-ID: | 4A2950C1.9020709@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
youngvonlee(at)gmail(dot)com wrote:
> On 6月4日, 下午1时52分, "youngvon(dot)(dot)(dot)(at)gmail(dot)com" <youngvon(dot)(dot)(dot)(at)gmail(dot)com>
> wrote:
>
>> i want to understand database knowledge about ipc,store,etc with a
>> project,ie,postgresql. I want to ask postgresql source code is very
>> good, is worth to learn .
>>
> I want to ask if postgresql source code is very well,and worth to
> learn with lots of times?
>
If I understand what you're asking correctly, yes, postgres source code
is generally quite good quality, clear, and well structured. that said,
its a rather large project with many intricate pieces that all fit
together. It may be difficult to see the layout of the forest when you
are down amongst the roots of the trees...
further, with regards to the overall algorithms and such, many are
unique to postgres, other databases approach the same general problem
(storage, transactions, etc) in quite different ways.
before digging into the source, you'll probably want to familiarize
yourself with
http://www.postgresql.org/docs/current/static/internals.html as this
explains many of the algorithms and design decisions that were made.
From | Date | Subject | |
---|---|---|---|
Next Message | Atul Chojar | 2009-06-05 17:12:15 | How to automatically propagate new/changed database functions from one database to another |
Previous Message | Jean Hoderd | 2009-06-05 17:00:31 | NOT NULL with CREATE TYPE |