> Hi all,
>
> For a few months now I've been thinking about whether or not a guide
> ('line-by-line') to the Postgres source tree would be of any value.
>
> Such a guide would, most probably, trace an 'ultimate' query (ie,
> one which requires the use of all source level functionality) through the
> source as well as reference appendices guides to underlying functionality
> (backend lib, transactions, macros) and client interfaces (inc. FE/BE
> protocol, internals of the libs etc), procedural language interfaces, SPI
> and any other part of the source I have left out.
I wonder if we should just work down from where we are now. We have the
FAQ, backend flowchard, and "PostgreSQL Internals through Pictures" that
I wrote, plus a presentation by Tom Lane. Where do we go from there?
> Secondly, where Postgres really out performs proprietary databases is in
> its source being open. Problems which cause major functionality problems
> and downtime in critical vendor installations could often easily be
> resolved if developers had the source. I think a thorough source guide
> would go some way to bolstering the appeal of Postgres to such developers
> whilst countering some of the arguments for throwing hefty sums of money
> at support.
I didn't realize that was happening.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
