diff options
Diffstat (limited to 'doc/FAQ_DEV')
-rw-r--r-- | doc/FAQ_DEV | 35 |
1 files changed, 20 insertions, 15 deletions
diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV index 37169e479b5..f3a9835cfff 100644 --- a/doc/FAQ_DEV +++ b/doc/FAQ_DEV @@ -1,7 +1,7 @@ Developer's Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Wed Jan 5 17:36:58 EST 2005 + Last updated: Fri Mar 11 16:43:05 EST 2005 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -9,8 +9,8 @@ http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html. _________________________________________________________________ - General Questions - +General Questions + 1.1) How do I get involved in PostgreSQL development? 1.2) What development environment is required to develop code? 1.3) What areas need work? @@ -31,8 +31,8 @@ 1.17) Where can I get technical assistance? 1.18) How do I get involved in PostgreSQL web site development? - Technical Questions - +Technical Questions + 2.1) How do I efficiently access information in tables from the backend code? 2.2) Why are table, column, type, function, view names sometimes @@ -46,7 +46,7 @@ General Questions - 1.1) How go I get involved in PostgreSQL development? + 1.1) How do I get involved in PostgreSQL development? Download the code and have a look around. See 1.7. @@ -97,6 +97,11 @@ have misunderstood the TODO item; your approach may benefit from the review of others. + A web site is maintained for patches that are ready to be applied, + http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are + being kept for the next release, + http://momjian.postgresql.org/cgi-bin/pgpatches2. + 1.5) Where can I learn more about the code? Other than documentation in the source tree itself, you can find some @@ -134,7 +139,7 @@ Basic system testing The easiest way to test your code is to ensure that it builds against - the latest verion of the code and that it does not generate compiler + the latest version of the code and that it does not generate compiler warnings. It is worth advised that you pass --enable-cassert to configure. This @@ -150,7 +155,7 @@ test suite. To do this, issue "make check" in the root directory of the source tree. If any tests failure, investigate. - If you've deliberately changed existing behaviour, this change may + If you've deliberately changed existing behavior, this change may cause a regression test failure but not any actual regression. If so, you should also patch the regression test suite. @@ -377,7 +382,7 @@ 1. A set of patches to make certain portions of the source tree 'behave' in the different environment of the RPMset; 2. The initscript; - 3. Any other ancilliary scripts and files; + 3. Any other ancillary scripts and files; 4. A README.rpm-dist document that tries to adequately document both the differences between the RPM build and the WHY of the differences, as well as useful RPM environment operations (like, @@ -495,7 +500,7 @@ want to contain the toplevel "pgsql" directory and say cvs ... checkout pgsql - To get a past branch, you cd to whereever you want it and say + To get a past branch, you cd to wherever you want it and say cvs ... checkout -r BRANCHNAME pgsql For example, just a couple days ago I did @@ -548,19 +553,19 @@ questions about development of new features, on IRC at irc.freenode.net in the #postgresql channel. - 1.18) How go I get involved in PostgreSQL web site development? + 1.18) How do I get involved in PostgreSQL web site development? PostgreSQL website development is discussed on the pgsql-www@postgresql.org mailing list. The is a project page where the source code is available at http://gborg.postgresql.org/project/pgweb/projdisplay.php , the code for the next version of the website is under the "portal" module. You - will al so find code for the "techdocs" website if you would like to + will also find code for the "techdocs" website if you would like to contribute to that. A temporary todo list for current website development issues is available at http://xzilla.postgresql.org/todo - Technical Questions - +Technical Questions + 2.1) How do I efficiently access information in tables from the backend code? You first need to find the tuples(rows) you are interested in. There @@ -653,7 +658,7 @@ typedef struct nameData Here are some of the List manipulation commands: lfirst(i), lfirst_int(i), lfirst_oid(i) - return the data (a point, inteter and OID respectively) at list + return the data (a point, integer and OID respectively) at list element i. lnext(i) |