From 189c3481c447bed619c96b7801f06f75fadf8fdd Mon Sep 17 00:00:00 2001
From: Bruce Momjian Last updated: Sat Oct 19 22:58:02 EDT 2002 Last updated: Sun Oct 20 20:47:14 EDT 2002 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) If you are doing many INSERTs, consider doing
them in a large batch using the COPY command. This
- is much faster than individual INSERTS. Second,
+ is much faster than individual INSERTS. Second,
statements not in a BEGIN WORK/COMMIT transaction
block are considered to be in their own transaction. Consider
performing several statements in a single transaction block. This
@@ -721,7 +716,7 @@
If postmaster is running, start psql in one
window, then find the PID of the postgres
process used by psql. Use a debugger to attach to the
- postgres PID. You can set breakpoints in the
+ postgres PID. You can set breakpoints in the
debugger and issue queries from psql. If you are debugging
postgres startup, you can set PGOPTIONS="-W n", then start
psql. This will cause startup to delay for n seconds
@@ -759,7 +754,7 @@
maximum number of processes, NPROC; the maximum
number of processes per user, MAXUPRC; and the
maximum number of open files, NFILE and
- NINODE. The reason that PostgreSQL has a limit on
+ NINODE. The reason that PostgreSQL has a limit on
the number of allowed backend processes is so your system won't run
out of resources.Frequently Asked Questions (FAQ) for PostgreSQL
-
@@ -80,9 +76,9 @@
clients" when trying to connect?
3.9) What is in the pgsql_tmp
directory?
- 3.10) Why do I need to do a dump and restore
+ 3.10) Why do I need to do a dump and restore
to upgrade PostgreSQL releases?
-
+
Operational Questions
4.1) What is the difference between binary
@@ -440,9 +436,8 @@
Features section above. We are built for reliability and
features, though we continue to improve performance in every
release. There is an interesting Web page comparing PostgreSQL to
- MySQL at
-
- http://openacs.org/why-not-mysql.html
+ MySQL at
+ http://openacs.org/philosophy/why-not-mysql.html
@@ -653,7 +648,7 @@
They are temporary files generated by the query executor. For - example, if a sort needs to be done to satisfy an ORDER - BY, and the sort requires more space than the backend's - -S parameter allows, then temporary files are created to - hold the extra data.
+This directory contains temporary files generated by the query + executor. For example, if a sort needs to be done to satisfy an + ORDER BY and the sort requires more space than the + backend's -S parameter allows, then temporary files are created + here to hold the extra data.
The temporary files are usually deleted automatically, but might remain if a backend crashes during a sort. A stop and restart of the @@ -815,7 +809,7 @@
The entire query may have to be evaluated, even if you only want the first few rows. Consider using a query that has an ORDER - BY. If there is an index that matches the ORDER + BY. If there is an index that matches the ORDER BY, PostgreSQL may be able to evaluate only the first few records requested, or the entire query may have to be evaluated until the desired rows have been generated.
@@ -955,22 +949,22 @@When using wild-card operators such as LIKE or - ~, indexes can only be used in certain circumstances: + ~, indexes can only be used in certain circumstances:
@@ -1342,7 +1336,7 @@ BYTEA bytea variable-length byte array (null-byte safe) Because PostgreSQL loads database-specific system catalogs, it is uncertain how a cross-database query should even behave.
-/contrib/dblink allows cross-database queries using +
contrib/dblink allows cross-database queries using function calls. Of course, a client can make simultaneous connections to different databases and merge the results on the client side.
@@ -1379,13 +1373,13 @@ BYTEA bytea variable-length byte array (null-byte safe)