From bb1095c66d48b492236993ce793371e3236d051e Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Thu, 15 Feb 2001 22:15:10 +0000
Subject: Update FAQ.
---
doc/src/FAQ/FAQ.html | 64 +++++++++++++---------------------------------------
1 file changed, 16 insertions(+), 48 deletions(-)
(limited to 'doc/src')
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index 4324be49e40..59ad51047f8 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -127,17 +127,15 @@
TID?
4.18) What is the meaning of some of the terms
used in PostgreSQL?
- 4.19) Why do I get the error "FATAL: palloc
- failure: memory exhausted?"
- 4.20) How do I tell what PostgreSQL version I
+ 4.19) How do I tell what PostgreSQL version I
am running?
- 4.21) My large-object operations get
+ 4.20) My large-object operations get
invalid large obj descriptor. Why?
- 4.22) How do I create a column that will
+ 4.21) How do I create a column that will
default to the current time?
- 4.23) Why are my subqueries using
+ 4.22) Why are my subqueries using
IN
so slow?
- 4.24) How do I perform an outer join?
+ 4.23) How do I perform an outer join?
A list of general database terms can be found at: http://www.comptechnews.com/~reaster/dbdesign.html
-It is possible you have run out of virtual memory on your - system, or your kernel has a low limit for certain resources. Try - this before starting the postmaster:
-- ulimit -d 65536 - limit datasize 64m -- Depending on your shell, only one of these may succeed, but it will - set your process data segment limit much higher and perhaps allow - the query to complete. This command applies to the current process, - and all subprocesses created after the command is run. If you are - having a problem with the SQL client because the - backend is returning too much data, try it before starting the - client. - -
From psql, type select version();
If you are using a client interface like ODBC you
may need to set auto-commit off.
IN
so slow?PostgreSQL 7.1 and later supports outer joins using the SQL @@ -1264,28 +1240,20 @@ BYTEA bytea variable-length byte array (null-safe)
The problem could be a number of things. Try testing your user-defined function in a stand-alone test program first.
-You are pfree'ing something that was not - palloc'ed. Beware of mixing malloc/free and - palloc/pfree.
- -Send your extensions to the pgsql-hackers mailing list, and they will eventually end up in the contrib/ subdirectory.
-This requires wizardry so extreme that the authors have never tried it, though in principle it can be done.
-The Makefiles do not have the proper dependencies for -- cgit v1.2.3