Update FAQ's for release.

1 files changed, 32 insertions, 31 deletions

diff --git a/doc/FAQ_HPUX b/doc/FAQ_HPUX
index ecd4270871f..4789c65e1dd 100644
--- a/doc/FAQ_HPUX
+++ b/doc/FAQ_HPUX
@@ -1,3 +1,4 @@
+
 =======================================================
 Frequently Asked Questions (FAQ) for PostgreSQL  V6.4
 HP-UX Specific
@@ -10,19 +11,19 @@ original author:        Tom Lane (tgl@sss.pgh.pa.us)
 
 
 Questions covered here:
-1.1)	What do I need to install PostgreSQL on HP-UX?
-1.2)	Anything special about the build/install procedure?
-1.3)	yacc dies trying to process src/backend/parser/gram.y.
-1.4)	Linking the main postgres executable fails, complaining that
-	there's no "alloca" function. 
-1.5)	OK, it seemed to build and install, but the regression test fails.
+1.1)    What do I need to install PostgreSQL on HP-UX?
+1.2)    Anything special about the build/install procedure?
+1.3)    yacc dies trying to process src/backend/parser/gram.y.
+1.4)    Linking the main postgres executable fails, complaining that
+        there's no "alloca" function.
+1.5)    OK, it seemed to build and install, but the regression test fails.
 
 
 ----------------------------------------------------------------------
 Section 1:      Installing PostgreSQL
 ----------------------------------------------------------------------
 
-1.1)	What do I need to install PostgreSQL on HP-UX?
+1.1)    What do I need to install PostgreSQL on HP-UX?
 
 PostgreSQL 6.4 is known to build and pass regression test on HPUX 9.03,
 9.05, and 10.20, given appropriate system patch levels and build tools.
@@ -53,14 +54,14 @@ install on HPUX, so I recommend you not bother with anything older
 than 6.4.
 
 
-1.2)	Anything special about the build/install procedure?
+1.2)    Anything special about the build/install procedure?
 
 When you run configure, you will want to explicitly select either the
 hpux_cc or hpux_gcc template depending on which compiler you plan to
 use:
-	./configure --with-template=hpux_cc
+        ./configure --with-template=hpux_cc
 for HP's C compiler, or
-	./configure --with-template=hpux_gcc
+        ./configure --with-template=hpux_gcc
 for GNU gcc.  (If you omit --with-template, configure may either
 default to hpux_cc or give up entirely, depending on which HPUX and
 PostgreSQL releases you have.)
@@ -86,7 +87,7 @@ Otherwise the standard build/install procedure described in the
 PostgreSQL documentation works fine.
 
 
-1.3)	yacc dies trying to process src/backend/parser/gram.y.
+1.3)    yacc dies trying to process src/backend/parser/gram.y.
 
 HP's yacc doesn't create its tables large enough to handle the Postgres
 grammar (a lot of other vendors' yaccs have this problem too).  There
@@ -106,15 +107,15 @@ are using HP's cc on HPUX 9 --- see next item.
 3. Increase yacc's table sizes enough to cope.  With a pre-6.4
 PostgreSQL grammar, I was able to get HPUX 9's yacc to work by
 setting YFLAGS to
-	-d -Np2000 -Ns3000 -Nm100000 -Nl2000 -Na30000 -Nc10000
+        -d -Np2000 -Ns3000 -Nm100000 -Nl2000 -Na30000 -Nc10000
 (You can edit YFLAGS either in the template file before running
 configure, or in src/Makefile.global afterwards.)  Future PostgreSQL
 releases might require even larger tables, but this should do for
 a starting point.
 
 
-1.4)	Linking the main postgres executable fails, complaining that
-	there's no "alloca" function. 
+1.4)    Linking the main postgres executable fails, complaining that
+        there's no "alloca" function.
 
 If you're using HP's cc on HPUX 9, it's right: there's no alloca
 function.  The only place in PostgreSQL that uses alloca is the parser
@@ -131,7 +132,7 @@ There are several possible answers:
      before Y2K anyway...
 
 
-1.5)	OK, it seemed to build and install, but the regression test fails.
+1.5)    OK, it seemed to build and install, but the regression test fails.
 
 There are several "expected failures" due to differences between HPUX
 and the regression test reference platform used by the PostgreSQL group.
@@ -139,26 +140,26 @@ A look at the textual differences between the expected and actual
 outputs will usually reveal that the differences are minor.  You should
 expect these differences:
 
-TEST(S)			COMMENTS
+TEST(S)                 COMMENTS
 
-int2, int4:		pg_atoi generates a differently worded error
-			message for integer overflow.
+int2, int4:             pg_atoi generates a differently worded error
+                        message for integer overflow.
 
-float8:			In 6.4, float8 shows some differences due to
-			different handling of overflow/underflow errors in
-			exp() and pow().  This should be fixed in 6.4.1
-			and later.
+float8:                 In 6.4, float8 shows some differences due to
+                        different handling of overflow/underflow errors in
+                        exp() and pow().  This should be fixed in 6.4.1
+                        and later.
 
-float8, geometry:	Lots of differences in the last digit or two
-			because of different roundoff errors in floating
-			arithmetic.  Also, HPUX does not distinguish
-			-0 from 0 during printout, but the reference
-			platform does.
+float8, geometry:       Lots of differences in the last digit or two
+                        because of different roundoff errors in floating
+                        arithmetic.  Also, HPUX does not distinguish
+                        -0 from 0 during printout, but the reference
+                        platform does.
 
-horology:		HPUX time library does not know about daylight
-			savings time before 1970, so there are some
-			places in horology where a time will be shown
-			in PST instead of PDT.
+horology:               HPUX time library does not know about daylight
+                        savings time before 1970, so there are some
+                        places in horology where a time will be shown
+                        in PST instead of PDT.
 
 In addition, the int8 regression test will fail massively on HPUX 9,
 because int8 doesn't actually work on this platform (sprintf/sscanf