From d90eb434e4b93ef679499e5f23b0c812f6a4a8f9 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sun, 21 Jan 2001 22:16:56 +0000 Subject: Update FAQ. --- doc/src/FAQ/FAQ.html | 112 +++++++++++++++++---------------------------------- 1 file changed, 38 insertions(+), 74 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index 0fce45f71ce..57038e4db7a 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -63,30 +63,27 @@
A file win31.mak is included in the distribution for + platforms. A file win31.mak is included in the distribution for making a Win32 libpq library and psql.
-The database server is now working on Windows NT using Cygwin, - the Cygnus Unix/NT porting library. See pgsql/doc/FAQ_NT in - the distribution. It does not work on MS Windows 9X because Cygwin - does not support the features we need on those platforms.
+The database server can run on Windows NT and later using + Cygwin, the Cygnus Unix/NT porting library. See pgsql/doc/FAQ_MSWIN + in the distribution. The database server does not run on MS Windows 9X + because Cygwin does not support the required features on those platforms. + We have no plans to do a native port to any Microsoft platform.
The latest release of PostgreSQL is version 7.0.2.
+The latest release of PostgreSQL is version 7.0.3.
We plan to have major releases every four months.
@@ -565,39 +561,19 @@Try these:
- -If you see an error message about oidvector, you - definately have a version mismatch.
- -The simplest way is to specify the --prefix option when running - configure. If you forgot to do that, you can edit - Makefile.global and change POSTGRESDIR accordingly, or - create a Makefile.custom and define POSTGRESDIR there.
+Specify the --prefix option when running configure.
-It could be a variety of problems, but first check to see that you have System V extensions installed in your kernel. PostgreSQL requires kernel support for shared memory and semaphores.
-You either do not have shared memory configured properly in your @@ -607,7 +583,7 @@ postmaster. For most systems, with default numbers of buffers and processes, you need a minimum of ~1MB.
-If the error message is something else, you might not have semaphore support configured in your kernel at all.
-By default, PostgreSQL only allows connections from the local @@ -633,7 +609,7 @@ modifying the file $PGDATA/pg_hba.conf accordingly. This will allow TCP/IP connections.
-The default configuration allows only unix domain socket @@ -642,21 +618,13 @@ option, and add an appropriate host entry to the file pgsql/data/pg_hba.conf.
-You should not create database users with user id 0 (root). They - will be unable to access the database. This is a security - precaution because of the ability of users to dynamically link - object modules into the database engine.
- -This problem can be caused by a kernel that is not configured to support semaphores.
-Certainly, indices can speed up queries. The @@ -693,7 +661,7 @@ data in tables to match an index. See the CLUSTER manual page for more details.
-PostgreSQL has several features that report status information @@ -749,7 +717,7 @@ in the pgsql/data/base/dbname directory. The client profile file will be put in the client's current directory.
-You need to increase the postmaster's limit on how many @@ -784,7 +752,7 @@ the MaxBackendId constant in include/storage/sinvaladt.h.
-They are temporary files generated by the query executor. For @@ -835,7 +803,7 @@
You can read the source code for psql in file - pgsql/src/bin/psql/psql.c. It contains SQL commands that + pgsql/src/bin/psql/describe.c. It contains SQL commands that generate the output for psql's backslash commands. You can also start psql with the -E option so it will print out the queries it uses to execute the commands you give.
@@ -860,20 +828,14 @@Maximum size for a database? unlimited (60GB databases exist) Maximum size for a table? unlimited on all operating systems -Maximum size for a row? 8k, configurable to 32k -Maximum number of rows in a table? unlimited +Maximum size for a row? unlimited in 7.1 and later +Maximum number of rows in a table? unlimited Maximum number of columns in a table? unlimited Maximum number of indexes on a table? unlimitedOf course, these are not actually unlimited, but limited to available disk space. -
To change the maximum row size, edit include/config.h and - change BLCKSZ. To use attributes larger than 8K, you - can also use the large object interface.
- -The row length limit will be removed in 7.1.
-PostgreSQL does not support outer joins in the current release. - They can be simulated using UNION and NOT +
PostgreSQL 7.1 and later supports outer joins. In previous releases, + outer joins can be simulated using UNION and NOT IN. For example, when joining tab1 and tab2, the following query does an outer join of the two tables:
@@ -1295,7 +1257,9 @@ BYTEA bytea variable-length byte array (null-safe)The Makefiles do not have the proper dependencies for include files. You have to do a make clean and then another - make.
+ make. If you are using GCC you can use the --enable-depend + option of configure to have the compiler compute the + dependencies automatically.