Revise platform FAQs.

doc/FAQ_AIX

 From: Zeugswetter Andreas <ZeugswetterA@spardat.at>
-Fri Sep 27 12:33:36 MSZ 2002
+$Date: 2002/11/11 20:04:05 $
 
 On AIX 4.3.2 PostgreSQL compiled with the native IBM compiler xlc
-(vac.C 5.0.1) passes all regression tests.
-Other versions of OS and compiler should also work. If you don't have a 
-powerpc or use gcc you might see rounding differences in the geometry
-regression test.
+(vac.C 5.0.1) passes all regression tests.  Other versions of OS and
+compiler should also work. If you don't have a powerpc or use gcc you
+might see rounding differences in the geometry regression test.
 
 Use the following configure flags in addition to your own
 if you have readline or libz there:
 --with-includes=/usr/local/include --with-libraries=/usr/local/lib
 
-If you need libpq++ and have trouble --with-CXX=xlC make sure you have
-installed the appropriate C++ include files and use a C++ version that
-supports the string class (e.g. VisualAge C++ filesets vacpp.cmp.batch 5.0
-and vacpp.cmp.include 5.0).
-
-There will probably be warnings about 0.0/0.0 division and duplicate symbols 
-which you can safely ignore.
+There will probably be warnings about 0.0/0.0 division and duplicate
+symbols which you can safely ignore.
 
 Compiling PostgreSQL with gcc (2.95.3) on AIX also works.
-Use the configure flags: --with-CC=gcc
 
-You need libm.a that is in the fileset bos.adt.libm (try following command)
+You need libm.a that is in the fileset bos.adt.libm.  (Try the
+following command.)
 $ lslpp -l bos.adt.libm
 
 Since the mktime() function does not work on AIX for dates before
-1970, all localtime formatted datetimes will not use summer time for
-dates before 1970.
+1970, all localtime formatted datetimes will not use daylight-saving
+time for dates before 1970.

doc/FAQ_HPUX

@@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL 7.3
 HP-UX Specific
 TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
 =======================================================
-last updated:           $Date: 2002/11/02 00:46:23 $
+last updated:           $Date: 2002/11/11 20:04:05 $
 
 current maintainer:     Tom Lane (tgl@sss.pgh.pa.us)
 original author:        Tom Lane (tgl@sss.pgh.pa.us)
@@ -48,9 +48,9 @@ ftp://us-ffs.external.hp.com/ for free copies of their latest patches.
 
 If you have both HP's C compiler and GCC's, then you might want to
 explicitly select the compiler to use when you run `configure':
-	CC=cc ./configure
+	./configure CC=cc
 for HP's C compiler, or
-	CC=gcc ./configure
+	./configure CC=gcc
 for GCC.  If you omit this setting, then configure will pick gcc
 if it has a choice.
 

doc/FAQ_IRIX

 =======================================================
-Frequently Asked Questions (FAQ) for PostgreSQL 7.2
+Frequently Asked Questions (FAQ) for PostgreSQL
 IRIX Specific
 TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
 =======================================================
-last updated:           $Date: 2001/12/19 18:50:48 $
+last updated:           $Date: 2002/11/11 20:04:05 $
 
 current maintainer:     Luis Amigo (lamigo@atc.unican.es)
 original author:        Luis Amigo (lamigo@atc.unican.es)
@@ -38,20 +38,7 @@ libgcc, but this has not been tested yet.
 
 1.2)	Anything special about the build/install procedure?
 
-In order to compile with cc you will need to execute:
-
-CC=cc ./configure
-
-You may want to edit src/templates/irix5 to include something like:
-
-CFLAGS='-O2'
-LDFLAGS='-O2'
-
-It is a good place to improve performance of PostgreSQK, because here you
-may use all MIPSPro power generating specific objects, see man cc.
-
-Another known problem is include location, it may be different from some
-compiler installations to others.  This may manifest itself with something like:
+There may be a compilation problem like the following:
 
 cc-1020 cc: ERROR File = pqcomm.c, Line = 427
   The identifier "TCP_NODELAY" is undefined.
@@ -69,7 +56,6 @@ There are several "expected failures" due to differences between your platform
 and the regression test reference platform used by the PostgreSQL group.  All
 of these should be compensated for by the regression test comparison
 mechanism, with the possible exception of some low-order-digit differences in
-the geometry tests (depending on which FPU are you using) or order differences
-between zero and NULL in join tests(depending on compiler version).
+the geometry tests (depending on which FPU are you using).
 
 Any other error is cause for suspicion.

doc/FAQ_MSWIN

 How to install PostgreSQL on Windows
 ====================================
-$Date: 2002/02/02 20:34:16 $
+$Date: 2002/11/11 20:04:05 $
 
 1.  Install the latest Cygwin package, available at http://cygwin.com/.
     The Cygwin package provides a UNIX-like API on top of the Win32
-    API.  Using older versions such as 1.0 or B20 might require extra
-    efforts.
+    API.
 
     A pre-built PostgreSQL is part of the standard Cygwin distribution
     and is installed by Cygwin's setup.exe.  You are encouraged to use

doc/FAQ_Solaris

 ============================================================
-Frequently Asked Questions (FAQ) for PostgreSQL 7.2
+Frequently Asked Questions (FAQ) for PostgreSQL
 Sun Solaris specific
 to be read in conjunction with the installation instructions
 ============================================================
-last updated:        $Date: 2002/07/27 20:10:03 $
+last updated:        $Date: 2002/11/11 20:04:05 $
 
 current maintainer:  Peter Eisentraut <peter_e@gmx.net>
 
@@ -13,7 +13,6 @@ Contents:
 1) What tools do I need to build and install PostgreSQL on Solaris?
 2) Why do I get problems when building with OpenSSL support?
 3) Why does configure complain about a failed test program?
-4) How do I ensure that pg_dump and pg_restore can handle files > 2 Gb?
 5) Why does my 64-bit build sometimes crash?
 
 
@@ -32,10 +31,10 @@ http://www.sunfreeware.com
 If you prefer sources, look here:
 http://www.gnu.org/order/ftp.html
 
-You can build with either GCC or Sun's compiler suite.  We have heard reports
-of problems when using gcc 2.95.1; gcc 2.95.3 is recommended.  If you are
-using Sun's compiler, be careful *not* to select /usr/ucb/cc; use
-/opt/SUNWspro/bin/cc.
+You can build with either GCC or Sun's compiler suite.  We have heard
+reports of problems when using gcc 2.95.1; gcc 2.95.3 or later is
+recommended.  If you are using Sun's compiler, be careful *not* to
+select /usr/ucb/cc; use /opt/SUNWspro/bin/cc.
 
 
 2) Why do I get problems when building with OpenSSL support?
@@ -72,18 +71,7 @@ Alternatively, set the environment variable LD_RUN_PATH.  See the
 ld(1) man page for more information.
 
 
-4) How do I ensure that pg_dump and pg_restore can handle files > 2 Gb?
-
-By default, gcc will build programs that only handle 32-bit file offsets.
-This is not a real problem for the server but can easily be trouble for
-pg_dump and pg_restore.  Before running 'configure', set your CFLAGS variable
-to specify support for files with 64-bit offsets.  This has been verified
-to work on Solaris 7:
-
-     CFLAGS="`getconf LFS_CFLAGS`"; export CFLAGS
-
-
-5) Why does my 64-bit build sometimes crash?
+4) Why does my 64-bit build sometimes crash?
 
 On Solaris 7 and older, the 64-bit version of libc has a buggy vsnprintf
 routine, which leads to erratic core dumps in PostgreSQL.  The simplest known