Linux-specific questions are answered in http://www.PostgreSQL.org/docs/faq-linux.html.
+HPUX-specific questions are answered in http://www.PostgreSQL.org/docs/faq-hpux.html.
+ +Solaris-specific questions are answered in http://www.postgresql.org/docs/faq-solaris.html.
+ Irix-specific questions are answered in http://www.PostgreSQL.org/docs/faq-irix.html.
-HPUX-specific questions are answered in http://www.PostgreSQL.org/docs/faq-hpux.shtml.
-
+There is a PostgreSQL book availiable at +http://www.postgresql.org/docs/awbook.html
+ psql has some nice \d commands to show information about types, operators, functions, aggregates, etc.
@@ -367,6 +374,10 @@ TODO for a list of known bugs, missing features, and future plans.
+The PostgreSQL book at +http://www.postgresql.org/docs/awbook.html teaches SQL. + There is a nice tutorial at http://w3.one.net/~jhoffman/sqltut.htm and at http://members.tripod.com/er4ebus/sql/index.htm
Many of our users like The Practical SQL Handbook, Bowman et al., -Addison Wesley. Others like Lan Times Guide to SQL, Groff et al., -Osborne McGraw-Hill.
+Addison Wesley. Others like The Complete Reference SQL, Groff et al., +McGraw-Hill.
@@ -484,20 +495,6 @@ add our code to your product with no limitations, except those outlined
in our BSD-style license stated above.
-
- -These are the limits: - -
-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 number of columns table? unlimited -Maximun number of indexes on a table? unlimited --The row length limit will be removed in 7.1.
-
WARN:heap_modifytuple: repl is
-\ 9, this is the problem.)
-@@ -848,15 +844,23 @@ this:
-Rows are limited to 8K bytes, but this can be changed by editing -include/config.h and changing BLCKSZ. To use attributes -larger than 8K, you can also use the large object interface.
+These are the limits: -Rows do not cross 8k boundaries so a 5k row will require 8k of -storage.
+
+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 number of columns table? unlimited +Maximun number of indexes on a table? unlimited ++ +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.
+ +Row length limit will be removed in 7.1.
-Table and database sizes are unlimited. There are many databases that -are tens of gigabytes, and probably some that are hundreds.
@@ -1056,7 +1060,8 @@ Similarly, you could retrieve the just-assigned SERIAL value with the currval
Finally, you could use the oid returned from the INSERT statement to lookup the default value, though this is probably the least portable approach. In perl, using DBI with Edmund Mergl's DBD::Pg module, the oid value is made available via $sth->{pg_oid_status} after $sth->execute().
-4.16.3) Wouldn't use of currval() and nextval() lead to a race condition with other concurrent backend processes?
+
No. That has been handled by the backends. @@ -1232,4 +1237,3 @@ have to do a make clean and then another make.