From 508f96f52998c6cb12cbf60a97f20900e6f8e8f0 Mon Sep 17 00:00:00 2001
From: Bruce Momjian Last updated: Thu Oct 27 09:48:14 EDT 2005 Last updated: Tue Nov 22 10:13:04 EST 2005 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Download the code and have a look around. See
- PostgreSQL is developed mostly in the C programming language. It
@@ -123,7 +123,7 @@
when you make a modification to a C header file, all files depend
upon that file are also rebuilt. Send an email to pgsql-hackers with a proposal for what you want
@@ -154,7 +154,7 @@
http://momjian.postgresql.org/cgi-bin/pgpatches2. Generate the patch in contextual diff format. If you are
unfamiliar with this, you might find the script
@@ -174,7 +174,7 @@
that, let us know and we will manually update the documentation when
the patch is applied. Other than documentation in the source tree itself, you can find
@@ -182,7 +182,7 @@
"http://www.postgresql.org/developer">
http://www.postgresql.org/developer. There are several ways to obtain the source tree. Occasional
@@ -197,7 +197,7 @@
"http://developer.postgresql.org/docs/postgres/cvs.html">
http://developer.postgresql.org/docs/postgres/cvs.html. Basic system testingDeveloper's Frequently Asked Questions (FAQ) for
PostgreSQL
-
@@ -79,7 +79,7 @@
General Questions
- 1.1) How do I get involved in PostgreSQL
+
1.1) How do I get involved in PostgreSQL
development?
1.2) What development environment is required
+
1.2) What development environment is required
to develop code?
1.3) What areas need work?
+ 1.3) What areas need work?
Outstanding features are detailed in the TODO list. This is located
in doc/TODO in the source distribution or at
@@ -134,7 +134,7 @@
archives, the SQL standards and the recommend texts (see 1.10).1.4) What do I do after choosing an item to
+
1.4) What do I do after choosing an item to
work on?
1.5) I've developed a patch, what next?
+ 1.5) I've developed a patch, what next?
1.6) Where can I learn more about the
+
1.6) Where can I learn more about the
code?
1.7) How do I download/update the current
+
1.7) How do I download/update the current
source tree?
1.8) How do I test my changes?
+ 1.8) How do I test my changes?
First, all the files in the src/tools directory are @@ -380,7 +380,7 @@ There is also a script called unused_oids in pgsql/src/include/catalog that shows the unused oids.
-I have four good books, An Introduction to Database @@ -394,7 +394,7 @@ on-line written by Jim Gray at http://www.benchmarkresources.com..
-The files configure and configure.in are part of the GNU autoconf package. Configure allows us to test for @@ -418,7 +418,7 @@ all files derived by configure are removed, so you see only the file contained in the source distribution.
-There are a variety of places that need to be modified to add a new port. First, start in the src/template directory. Add an @@ -437,7 +437,7 @@ handling. There is a backend/port directory if you need special files for your OS.
-This was written by Lamar Owen:
@@ -576,7 +576,7 @@Of course, there are many projects that DO include all the files necessary to build RPMs from their Official Tarball (TM).
-This was written by Tom Lane:
@@ -646,7 +646,7 @@ dot-release or two, so that we won't have to double-patch the first wave of fixes. -There are three versions of the SQL standard: SQL-92, SQL:1999, @@ -683,7 +683,7 @@ (paper) -
Many technical questions held by those new to the code have been @@ -698,7 +698,7 @@ questions about development of new features, on IRC at irc.freenode.net in the #postgresql channel.
-PostgreSQL website development is discussed on the @@ -714,7 +714,7 @@
You first need to find the tuples(rows) you are interested in. @@ -782,7 +782,7 @@ ReleaseBuffer(), in the heap_fetch() case. Or it may be a palloc'ed tuple, that you must pfree() when finished. -
We do this because this allows a consistent way to pass data @@ -902,7 +902,7 @@ The output appears in the postmaster log file, or on your screen if you are running a backend directly without a postmaster. -
The structures passing around from the parser, rewrite, @@ -914,7 +914,7 @@ places the structure might need code for your new field. mkid is helpful with this (see 1.9).
-palloc() and pfree() are used in place of malloc() @@ -925,7 +925,7 @@ memory can be allocated in. These affect when the allocated memory is freed by the backend.
-ereport() is used to send messages to the front-end, and optionally terminate the current query being processed. The first @@ -944,7 +944,7 @@ descriptors so you don't need to clean these up before the call.
-Normally, transactions can not see the rows they modify. This
allows UPDATE foo SET x = x + 1
to work correctly.
First, try running configure with the --enable-cassert -- cgit v1.2.3