From 1ab96739beb8fdc711671dff0ea424e7bfa95999 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 22 Nov 2005 15:04:25 +0000 Subject: Update FAQ to explain process of submitting bug and feature requests. --- doc/src/FAQ/FAQ.html | 112 +++++++++++++++++++++++++++++++++++++-------------- 1 file changed, 82 insertions(+), 30 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index d3c5246069c..6f3fd77d5cb 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -10,7 +10,7 @@ alink="#0000ff">

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) @@ -145,6 +145,18 @@ 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?

@@ -205,6 +217,13 @@ 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 @@ -234,13 +253,65 @@ "ftp://ftp.PostgreSQL.org/pub/">ftp://ftp.PostgreSQL.org/pub/ to see if there is a more recent PostgreSQL version.

-

1.6) What is the latest release?

- -

The latest release of PostgreSQL is version 8.1.1

+

Bugs submitted using the bug form or posted to any PostgreSQL mailing + list typically generates one of the following replies:

+ + +

1.9) How do I find out about known bugs or + missing features?

-

We plan to have a major release every year, with minor releases - every few months.

+

PostgreSQL supports an extended subset of SQL:2003. + See our TODO + list for known bugs, missing features, and future plans.

+

A feature request usually results in one of the following + replies:

+ + +

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?

PostgreSQL includes extensive documentation, including a large @@ -267,13 +338,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?

@@ -359,18 +423,6 @@ -

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

@@ -1023,11 +1075,11 @@ length

The most common cause is the use of double-quotes around table or column names during table creation. When double-quotes are used, table and column names (called identifiers) are stored case-sensitive, meaning you must use - double-quotes when referencing the names in a query. Some interfaces, - like pgAdmin, automatically double-quote identifiers during table - creation. So, for identifiers to be recognized, you must either: + href="http://www.postgresql.org/docs/8.0/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS"> + case-sensitive, meaning you must use double-quotes when + referencing the names in a query. Some interfaces, like pgAdmin, + automatically double-quote identifiers during table creation. So, + for identifiers to be recognized, you must either: