diff options
Diffstat (limited to 'doc/FAQ')
| -rw-r--r-- | doc/FAQ | 79 |
1 files changed, 58 insertions, 21 deletions
@@ -1,7 +1,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Mon Nov 21 16:01:05 EST 2005 + Last updated: Tue Nov 22 10:04:06 EST 2005 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -101,6 +101,17 @@ company. To get involved, see the developer's FAQ at http://www.postgresql.org/files/documentation/faqs/FAQ_DEV.html + 1.2) Who controls PostgreSQL? + + If you are looking for a PostgreSQL gatekeeper, central committee, or + controlling company, give up --- there isn't one. We do have a core + committee and CVS committers, but these groups are more for + administrative purposes than control. The project is directed by the + community of developers and users, which anyone can join. All you need + to do is subscribe to the mailing lists and participate in the + discussions. (See the Developer's FAQ for information on how to get + involved in PostgreSQL development.) + 1.3) What is the copyright of PostgreSQL? PostgreSQL is distributed under the classic BSD license. Basically, it @@ -157,6 +168,13 @@ Via web browser, use http://www.postgresql.org/ftp/, and via ftp, use ftp://ftp.PostgreSQL.org/pub/. + 1.6) What is the latest release? + + The latest release of PostgreSQL is version 8.1.1 + + We plan to have a major release every year, with minor releases every + few months. + 1.7) Where can I get support? The PostgreSQL community provides assistance to many of its users via @@ -181,12 +199,47 @@ Also check out our ftp site ftp://ftp.PostgreSQL.org/pub/ to see if there is a more recent PostgreSQL version. - 1.6) What is the latest release? + Bugs submitted using the bug form or posted to any PostgreSQL mailing + list typically generates one of the following replies: + * It is not a bug, and why + * It is a known bug and is known already on the TODO list + * The bug has been fixed in the current release + * The bug has been fixed but is not packaged yet in an official + release + * A request is made for more detailed information: + + Operating system + + PostgreSQL version + + Reproducible test case + + Debugging information + + Debugger backtrace output + * The bug is new. The following might happen: + + A patch has been created and will be included in the next + major or minor release + + The bug cannot be fixed immediately and is added to the TODO + list + + 1.9) How do I find out about known bugs or missing features? - The latest release of PostgreSQL is version 8.1.1 + PostgreSQL supports an extended subset of SQL:2003. See our TODO list + for known bugs, missing features, and future plans. - We plan to have a major release every year, with minor releases every - few months. + A feature request usually results in one of the following replies: + * The feature is already on the TODO list + * The feature is not desired because: + + It duplicates existing functionality that already follows the + SQL standard + + The feature would increase code complexity but add little + benefit + + The feature would be insecure or unreliable + * The new feature is added to the TODO list + + PostgreSQL does not use a bug tracking system because we find it more + efficient to respond directly to email and keep the TODO list + up-to-date. In practice, bugs don't last very long in the software, + and bugs that affect a large number of users are fixed rapidly. The + only single place to find all changes, improvements, and fixes in a + PostgreSQL release is to read our CVS logs messages. Even the release + notes do not contain every change made to the software. 1.10) What documentation is available? @@ -209,11 +262,6 @@ Our web site contains even more documentation. - 1.9) How do I find out about known bugs or missing features? - - PostgreSQL supports an extended subset of SQL:2003. See our TODO list - for known bugs, missing features, and future plans. - 1.11) How can I learn SQL? First, consider the PostgreSQL-specific books mentioned above. Another @@ -273,17 +321,6 @@ We are free for all use, both commercial and non-commercial. You can add our code to your product with no limitations, except those outlined in our BSD-style license stated above. - - 1.2) Who controls PostgreSQL? - - If you are looking for a PostgreSQL gatekeeper, central committee, or - controlling company, give up --- there isn't one. We do have a core - committee and CVS committers, but these groups are more for - administrative purposes than control. The project is directed by the - community of developers and users, which anyone can join. All you need - to do is subscribe to the mailing lists and participate in the - discussions. (See the Developer's FAQ for information on how to get - involved in PostgreSQL development.) _________________________________________________________________ User Client Questions |