head	1.13;
access;
symbols
	REL7_4_29:1.9
	REL8_0_25:1.11
	REL8_1_21:1.11
	REL8_2_17:1.11.8.10
	REL8_3_11:1.12
	REL7_4_28:1.9
	REL8_0_24:1.11
	REL8_1_20:1.11
	REL8_2_16:1.11.8.10
	REL8_3_10:1.12
	REL7_4_27:1.9
	REL8_0_23:1.11
	REL8_1_19:1.11
	REL8_2_15:1.11.8.10
	REL8_3_9:1.12
	REL7_4_26:1.9
	REL8_0_22:1.11
	REL8_1_18:1.11
	REL8_2_14:1.11.8.10
	REL8_3_8:1.12
	REL7_4_25:1.9
	REL8_0_21:1.11
	REL8_1_17:1.11
	REL8_2_13:1.11.8.10
	REL8_3_7:1.12
	REL7_4_24:1.9
	REL8_0_20:1.11
	REL8_1_16:1.11
	REL8_2_12:1.11.8.10
	REL8_3_6:1.12
	REL7_4_23:1.9
	REL8_0_19:1.11
	REL8_1_15:1.11
	REL8_2_11:1.11.8.10
	REL8_3_5:1.12
	REL7_4_22:1.9
	REL8_0_18:1.11
	REL8_1_14:1.11
	REL8_2_10:1.11.8.10
	REL8_3_4:1.12
	REL7_4_21:1.9
	REL8_0_17:1.11
	REL8_1_13:1.11
	REL8_2_9:1.11.8.10
	REL8_3_3:1.12
	REL7_4_20:1.9
	REL8_0_16:1.11
	REL8_1_12:1.11
	REL8_2_8:1.11.8.10
	REL8_3_2:1.12
	REL8_2_7:1.11.8.10
	REL8_3_1:1.12
	REL8_3_STABLE:1.12.0.2
	REL8_3_0:1.12
	REL8_3_RC2:1.12
	REL7_3_21:1.8.4.5
	REL7_4_19:1.9
	REL8_0_15:1.11
	REL8_1_11:1.11
	REL8_2_6:1.11.8.10
	REL8_3_RC1:1.12
	REL8_3_BETA4:1.12
	REL8_3_BETA3:1.12
	REL8_3_BETA2:1.12
	REL8_3_BETA1:1.12
	REL7_3_20:1.8.4.5
	REL7_4_18:1.9
	REL8_0_14:1.11
	REL8_1_10:1.11
	REL8_2_5:1.11.8.10
	REL7_3_19:1.8.4.5
	REL7_4_17:1.9
	REL8_0_13:1.11
	REL8_1_9:1.11
	REL8_2_4:1.11.8.7
	REL8_0_12:1.11
	REL8_1_8:1.11
	REL8_2_3:1.11.8.6
	REL7_3_18:1.8.4.5
	REL7_4_16:1.9
	REL8_0_11:1.11
	REL8_1_7:1.11
	REL8_2_2:1.11.8.4
	REL8_0_10:1.11
	REL8_1_6:1.11
	REL8_2_1:1.11.8.3
	REL7_4_15:1.9
	REL7_3_17:1.8.4.5
	REL8_2_STABLE:1.11.0.8
	REL8_2_0:1.11
	REL8_2_RC1:1.11
	REL8_2_BETA3:1.11
	REL8_2_BETA2:1.11
	REL8_1_5:1.11
	REL8_0_9:1.11
	REL7_4_14:1.9
	REL7_3_16:1.8.4.5
	REL8_2_BETA1:1.11
	REL7_3_15:1.8.4.5
	REL7_4_13:1.9
	REL8_0_8:1.11
	REL8_1_4:1.11
	REL7_3_14:1.8.4.5
	REL7_4_12:1.9
	REL8_0_7:1.11
	REL8_1_3:1.11
	REL7_3_13:1.8.4.5
	REL7_4_11:1.9
	REL8_0_6:1.11
	REL8_1_2:1.11
	REL7_3_12:1.8.4.5
	REL7_4_10:1.9
	REL8_0_5:1.11
	REL8_1_1:1.11
	REL8_1_STABLE:1.11.0.6
	REL8_1_0:1.11
	REL8_1_0RC1:1.11
	REL8_1_0BETA4:1.11
	REL8_1_0BETA3:1.11
	REL7_3_11:1.8.4.5
	REL7_4_9:1.9
	REL8_0_4:1.11
	REL8_1_0BETA2:1.11
	REL8_1_0BETA1:1.11
	REL7_2_8:1.8
	REL7_3_10:1.8.4.5
	REL7_4_8:1.9
	REL8_0_3:1.11
	REL8_0_2:1.11
	REL7_2_7:1.8
	REL7_3_9:1.8.4.5
	REL7_4_7:1.9
	REL8_0_1:1.11
	REL8_0_STABLE:1.11.0.4
	REL8_0_0:1.11.0.2
	REL8_0_0RC5:1.11
	REL8_0_0RC4:1.11
	REL8_0_0RC3:1.11
	REL8_0_0RC2:1.11
	REL8_0_0RC1:1.11
	REL8_0_0BETA5:1.11
	REL8_0_0BETA4:1.11
	REL7_4_6:1.9
	REL7_3_8:1.8.4.5
	REL7_2_6:1.8
	REL8_0_0BETA3:1.11
	REL8_0_0BETA2:1.11
	REL7_2_5:1.8
	REL7_4_5:1.9
	REL7_3_7:1.8.4.5
	REL7_4_4:1.9
	REL8_0_0BETA1:1.11
	REL7_4_3:1.9
	REL7_4_2:1.9
	REL7_3_6:1.8.4.5
	REL7_4_1:1.9
	REL7_3_5:1.8.4.5
	REL7_4:1.9
	REL7_4_RC2:1.9
	REL7_4_STABLE:1.9.0.4
	REL7_4_RC1:1.9
	REL7_4_BETA5:1.9
	REL7_4_BETA4:1.9
	REL7_4_BETA3:1.9
	REL7_4_BETA2:1.9
	WIN32_DEV:1.9.0.2
	REL7_4_BETA1:1.9
	REL7_3_4:1.8.4.5
	REL7_3_2:1.8.4.3
	REL7_2_4:1.8
	REL7_3_STABLE:1.8.0.4
	REL7_2_3:1.8
	REL7_2_STABLE:1.8.0.2
	REL7_2:1.8
	REL7_2_RC2:1.8
	REL7_2_RC1:1.8
	REL7_2_BETA5:1.8
	REL7_2_BETA4:1.8
	REL7_2_BETA3:1.8
	REL7_2_BETA2:1.8
	REL7_2_BETA1:1.8
	REL7_1_2:1.7
	REL7_1_STABLE:1.7.0.2
	REL7_1_BETA:1.6
	REL7_1_BETA3:1.6
	REL7_1_BETA2:1.6
	REL7_1:1.7
	REL7_0_PATCHES:1.4.0.2
	REL7_0:1.4
	REL6_5_PATCHES:1.1.0.2
	REL6_5:1.1;
locks; strict;
comment	@# @;


1.13
date	2008.11.21.16.46.19;	author petere;	state dead;
branches;
next	1.12;

1.12
date	2006.12.05.14.47.34;	author momjian;	state Exp;
branches;
next	1.11;

1.11
date	2004.08.04.21.33.39;	author tgl;	state Exp;
branches
	1.11.8.1;
next	1.10;

1.10
date	2004.05.20.04.19.26;	author momjian;	state Exp;
branches;
next	1.9;

1.9
date	2002.11.08.16.49.15;	author momjian;	state Exp;
branches;
next	1.8;

1.8
date	2001.08.29.19.14.39;	author petere;	state Exp;
branches
	1.8.4.1;
next	1.7;

1.7
date	2001.03.13.20.52.04;	author petere;	state Exp;
branches;
next	1.6;

1.6
date	2000.10.09.03.49.42;	author momjian;	state Exp;
branches;
next	1.5;

1.5
date	2000.08.26.19.34.24;	author petere;	state Exp;
branches;
next	1.4;

1.4
date	2000.05.03.03.45.54;	author momjian;	state Exp;
branches;
next	1.3;

1.3
date	2000.05.02.10.57.11;	author momjian;	state Exp;
branches;
next	1.2;

1.2
date	2000.04.24.23.33.07;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	99.05.27.16.05.38;	author thomas;	state Exp;
branches;
next	;

1.8.4.1
date	2002.11.08.16.49.50;	author momjian;	state Exp;
branches;
next	1.8.4.2;

1.8.4.2
date	2002.11.16.02.34.22;	author momjian;	state Exp;
branches;
next	1.8.4.3;

1.8.4.3
date	2002.12.18.20.39.31;	author momjian;	state Exp;
branches;
next	1.8.4.4;

1.8.4.4
date	2003.02.14.14.05.52;	author momjian;	state Exp;
branches;
next	1.8.4.5;

1.8.4.5
date	2003.07.23.04.13.11;	author momjian;	state Exp;
branches;
next	;

1.11.8.1
date	2006.12.11.22.48.07;	author momjian;	state Exp;
branches;
next	1.11.8.2;

1.11.8.2
date	2007.01.05.20.55.28;	author momjian;	state Exp;
branches;
next	1.11.8.3;

1.11.8.3
date	2007.01.05.20.57.17;	author momjian;	state Exp;
branches;
next	1.11.8.4;

1.11.8.4
date	2007.02.01.04.56.41;	author momjian;	state Exp;
branches;
next	1.11.8.5;

1.11.8.5
date	2007.02.06.18.38.04;	author momjian;	state Exp;
branches;
next	1.11.8.6;

1.11.8.6
date	2007.02.07.03.16.59;	author momjian;	state Exp;
branches;
next	1.11.8.7;

1.11.8.7
date	2007.04.19.03.07.22;	author momjian;	state Exp;
branches;
next	1.11.8.8;

1.11.8.8
date	2007.09.11.17.37.29;	author momjian;	state Exp;
branches;
next	1.11.8.9;

1.11.8.9
date	2007.09.12.03.11.49;	author momjian;	state Exp;
branches;
next	1.11.8.10;

1.11.8.10
date	2007.09.13.03.34.23;	author momjian;	state Exp;
branches;
next	;


desc
@@


1.13
log
@Include the platform "FAQs" into the installation instructions.
I weeded out some really old information along the way.
FAQ_AIX needs separate consideration and will be dealt with later.
@
text
@=======================================================
Frequently Asked Questions (FAQ) for PostgreSQL
IRIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
last updated:           $Date: 2006/12/05 14:47:34 $

current maintainer:     Billy G. Allie (Bill.Allie@@mug.org)
original author:        Andrew Merrill (andrew@@compclass.com)


Consult http://buildfarm.postgresql.org/ for latest information.

PostgreSQL 8.0 can be built on SCO UnixWare 7 and SCO OpenServer 5.
On OpenServer, you can use either the OpenServer Development Kit or 
the Universal Development Kit.

However, some tweaking may be needed, as described below.

Topics:
*) Skunkware
*) GNU Make
*) Readline
*) Using the UDK on OpenServer
*) Compiling PostgreSQL using the UDK
*) Reading the PostgreSQL man pages
*) C99 Issues with the 7.1.1b Feature Supplement 
*) --enable-thread-safety and UnixWare
*) float4/float8 regression failures on NaN and inf I/O.


***************************************************************************
*) Skunkware

You should locate your copy of the SCO Skunkware CD.  The Skunkware CD is
included with UnixWare 7 and current versions of OpenServer 5.

Skunkware includes ready-to-install versions of many popular programs that
are available on the Internet.  For example, gzip, gunzip, GNU make, flex,
and bison are all included.

If you do not have this CD, the software on it is available via anonymous
ftp from ftp.sco.com/skunkware.

For UnixWare 7.1, this CD is now labeled "Open License Software Supplement".

Skunkware has different versions for UnixWare and OpenServer.  Make sure
you install the correct version for your operating system, except as noted
below.

Note: on UnixWare 7.1.3 and beyond, the GCC compiler is included on the UDK
CD as is GNUMake.

***************************************************************************
*) GNU Make

You need to use the GNU make program, which is on the Skunkware CD.  By
default, it installs as /usr/local/bin/make.  To avoid confusion with the
SCO make program, you may want to rename GNU make to gmake.

As of UnixWare 7.1.3 and above, the GNU Make program is is the OSTK portion
of the UDK CD, and is in /usr/gnu/bin/gmake.


***************************************************************************
*) Readline

If you install the readline library, then psql (the PostgreSQL command line
SQL interpreter) remembers each command you type, and allows you to use
arrow keys to recall and edit previous commands.  This is very helpful, and
is strongly recommended.  The readline library is on the Skunkware CD.

The readline library is not included on the UnixWare 7.1 Skunkware CD.  If
you have the UnixWare 7.0.0 or 7.0.1 Skunkware CDs, you can install it from
there.  Otherwise, try ftp.sco.com/skunkware.

By default, readline installs into /usr/local/lib and /usr/local/include.
However, the PostgreSQL configure program will not find it there without
help.  If you installed readline, then use the following options to
configure:

configure --with-libs=/usr/local/lib --with-includes=/usr/local/include


***************************************************************************
*) Using the UDK on OpenServer

If you are using the new Universal Development Kit (UDK) compiler on
OpenServer, you need to specify the locations of the UDK libraries:

configure --with-libs=/udk/usr/lib --with-includes=/udk/usr/include

Putting these together with the readline options from above:

./configure --with-libs="/udk/usr/lib /usr/local/lib" --with-includes="/udk/usr/include /usr/local/include"


***************************************************************************
*) Compiling PostgreSQL 7.1 with the UDK

The program, backend/utils/adt/int8.c, tickles a compiler bug with in the
following versions (and probably others as well) of the C compiler:

	Optimizing C Compilation System  (CCS) 3.2  08/18/98
	Optimizing C Compilation System  (CCS) 3.2  09/28/99 

If you encounter an error compiling backend/utils/adt/int8.c, please apply
the following patch:

------------------------------8< CUT HERE >8------------------------------
*** src/backend/utils/adt/int8.c.orig	Sat Oct  7 20:48:17 2000
--- src/backend/utils/adt/int8.c	Sat Oct  7 20:52:03 2000
***************
*** 489,495 ****
  	if (arg1 < 1)
  		result = 0;
  	else
! 		for (i = arg1, result = 1; i > 0; --i)
  			result *= i;
  
  	PG_RETURN_INT64(result);
--- 489,495 ----
  	if (arg1 < 1)
  		result = 0;
  	else
! 		for (i = arg1, result = 1; i; --i)
  			result *= i;
  
  	PG_RETURN_INT64(result);
------------------------------8< CUT HERE >8------------------------------

This compiler bug seems to be fixed at least in

	Optimizing C Compilation System  (CCS) 4.0  10/23/00 (UDK FS 7.1.1b) 


***************************************************************************
*) Reading the PostgreSQL man pages

By default, the PostgreSQL man pages are installed into
/usr/local/pgsql/man.  By default, UnixWare does not look there for
man pages.  To be able to read them you need to modify the MANPATH
variable in /etc/default/man.  I use:

	MANPATH=/usr/lib/scohelp/%L/man:/usr/dt/man:/usr/man:/usr/share/man:scohelp:/usr/local/man:/usr/local/pgsql/man

On OpenServer, some extra research needs to be invested to make the
man pages usable, because the man system is a bit different from other
platforms.  Currently, PostgreSQL will not install them at all.


***************************************************************************
*) C99 Issues with the 7.1.1b Feature Supplement 

For compilers earlier than the one released with OpenUNIX 8.0.0(UnixWare
7.1.2), Including the 7.1.1b Feature Supplement, you may need to specify -Xb
 in CFLAGS or the  CC environment variable.  The indication of this is an
error in compiling tuplesort.c referencing inline functions. 

Apparently there was a change in the 7.1.2(8.0.0) compiler and beyond.


***************************************************************************
*) --enable-thread-safety and UnixWare

If you use the --enable-thread-safety configure flag, you *MUST* use -Kpthread
on ALL libpq using programs.

libpq uses pthread_* calls, which are only available with the
-Kpthread/-Kthread flag.

***************************************************************************
*) float4/float8 regression failures on NaN and inf I/O.

You will see regression failures for the float4 and float8 regression
tests on the NaN and inf I/O functions.  This is due to a bug in SCO's strtod
library function on BOTH UnixWare and OpenServer.  It's slated to be fixed
in the first maintenance / update for UnixWare 7.1.4, and probably the
next MP/UP for OpenServer 5.0.7 (I'm not sure on the OSR side as of the time
I'm writing this (2004-05-14).

You might also see Join test failures due to ordering differences, and these
are ok.


@


1.12
log
@Update of port patches, HEAD patch only.

Simon Riggs
@
text
@d6 1
a6 1
last updated:           $Date: 2004/08/04 21:33:39 $
@


1.11
log
@Label CVS tip as 8.0devel instead of 7.5devel.  Adjust various comments
and documentation to reference 8.0 instead of 7.5.
@
text
@d1 6
a6 6
============================================================
Frequently Asked Questions (FAQ) for PostgreSQL 7.3
SCO UnixWare and OpenServer specific
to be read in conjunction with the installation instructions
============================================================
last updated:           $Date: 2004/05/20 04:19:26 $
d12 2
@


1.11.8.1
log
@Backpatch FAQ entry for null concatenation.
@
text
@d1 6
a6 6
=======================================================
Frequently Asked Questions (FAQ) for PostgreSQL
IRIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
last updated:           $Date: 2006/12/05 14:47:34 $
a11 2
Consult http://buildfarm.postgresql.org/ for latest information.

@


1.11.8.2
log
@Stamp release 8.2.1.  Update FAQs.
@
text
@@


1.11.8.3
log
@Update Japanese FAQ.
@
text
@@


1.11.8.4
log
@Backpatch FAQs to stable branch.
@
text
@@


1.11.8.5
log
@Backpatch FAQs to 8.2.X branch.
@
text
@@


1.11.8.6
log
@Update FAQ for 8.2.3.
@
text
@@


1.11.8.7
log
@Stamp releases 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19.
@
text
@@


1.11.8.8
log
@Stamp releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20.

Update FAQs for 8.2.5.
@
text
@@


1.11.8.9
log
@Update Japanese FAQ to current release number.
@
text
@@


1.11.8.10
log
@Update Japanese FAQ, backpatch.

Jun Kuwamura
@
text
@@


1.10
log
@Update SCO FAQ.

Larry Rosenman
@
text
@d6 1
a6 1
last updated:           $Date: 2002/11/08 16:49:15 $
d12 1
a12 1
PostgreSQL 7.5 can be built on SCO UnixWare 7 and SCO OpenServer 5.
@


1.9
log
@Update FAQ_SCO from Larry Rosenman, correction from Tom Lane.
@
text
@d6 1
a6 1
last updated:           $Date: 2001/08/29 19:14:39 $
d12 1
a12 1
PostgreSQL 7.3 can be built on SCO UnixWare 7 and SCO OpenServer 5.
d26 2
d49 2
d59 3
d159 24
@


1.8
log
@Install the SQL command man pages into a section appropriate for each
system.  Some systems did not understand the 'l' section, and in general
it wasn't entirely appropriate.

On SCO OpenServer, the man pages won't be installed at all until someone
figures out their man system.
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL 7.2
d6 1
a6 1
last updated:           $Date: 2001/03/13 20:52:04 $
d12 1
a12 1
PostgreSQL 7.1 can be built on SCO UnixWare 7 and SCO OpenServer 5.
d25 1
d141 12
@


1.8.4.1
log
@Update FAQ_SCO from Larry Rosenman, correction from Tom Lane.
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL 7.3
d6 1
a6 1
last updated:           $Date: 2001/08/29 19:14:39 $
d12 1
a12 1
PostgreSQL 7.3 can be built on SCO UnixWare 7 and SCO OpenServer 5.
a24 1
*) C99 Issues with the 7.1.1b Feature Supplement 
a139 12


***************************************************************************
*) C99 Issues with the 7.1.1b Feature Supplement 

For compilers earlier than the one released with OpenUNIX 8.0.0(UnixWare
7.1.2), Including the 7.1.1b Feature Supplement, you may need to specify -Xb
 in CFLAGS or the  CC environment variable.  The indication of this is an
error in compiling tuplesort.c referencing inline functions. 

Apparently there was a change in the 7.1.2(8.0.0) compiler and beyond.

@


1.8.4.2
log
@Update TODO/FAQ for 7.3 release.
@
text
@d6 1
a6 1
last updated:           $Date: 2002/11/08 16:49:15 $
@


1.8.4.3
log
@Update Russian FAQ.  Update all FAQ's for 7.3.X branch.
@
text
@@


1.8.4.4
log
@Update FAQ's in head and 7.3.X.
@
text
@@


1.8.4.5
log
@Update all FAQ's for 7.3.4.
@
text
@@


1.7
log
@update
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL  V7.1
d6 1
a6 1
last updated:           $Date: 2000/10/09 03:49:42 $
d24 1
a24 1
*) Reading the PostgreSQL man pages on UnixWare
d128 1
a128 1
*) Reading the PostgreSQL man pages on UnixWare
d130 4
a133 8
By default, the PostgreSQL man pages are installed into /usr/local/pgsql/man.
By default, UnixWare does not look there for man pages, so you will not be
able to read them.

You need to make the following changes to access the PostgreSQL man pages
from UnixWare.

1) You need to modify the MANPATH variable in /etc/default/man.  I use:
d137 3
a139 36
2) Add a line that says '1sql' to /etc/default/manSection.

3) The man pages for SQL commands are, by default, placed in section 'l'
   (normally used for "l"ocal pages).  UnixWare does not support the 'l'
   section.

The solution I use is to move all these pages from section 'l' to a section
named '1sql'.  To following KSH script will perform the move and change the
section names in the man page:

------------------------------8< CUT HERE >8------------------------------
#!/bin/ksh
cd /usr/local/pgsql/man
mv man1 man.1
mkdir man.1sql

cd /usr/local/pgsql/man/manl
for i in *.l
do
	sed -e '/^\.TH/s/"l"/"1sql"/'	\
		-e 's/\\fR(l)/\\fR(1sql)/' $i >../man.1sql/${i%.l}.1sql
done
cd /usr/local/pgsql/man
rm -rf manl
/usr/ucb/catman -M /usr/local/pgsql/man 1
/usr/ucb/catman -M /usr/local/pgsql/man 1sql
------------------------------8< CUT HERE >8------------------------------

After running this script, you can view the man pages using the 'man'
command.  They will not be usable from the scohelp system.

I am working on integrating the man pages into the scohelp system.  When I
generate a PostgreSQL package for UnixWare 7.x, the man pages will be
integrated into the scohelp system.

I have not tried using the PostgreSQL man pages on OpenServer.  Volunteers??
@


1.6
log
@I have compiled and tested PostgreSQL 7.1devel on UnixWare 7.1.  During the
process, the need for changes to the FAQ_SCO document was uncovered.  The
attach patch file implements thost changes.

Billy G. Allie
@
text
@d1 6
a6 6
=======================================================
Frequently Asked Questions (FAQ) for PostgreSQL  V7.0
SCO UnixWare and OpenServer Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
last updated:           $Date: 2000/08/26 19:34:24 $
d12 1
a12 1
PostgreSQL 7.0 can be built on SCO UnixWare 7 and SCO OpenServer 5.
a20 1
*) C++ and libpq++
d46 1
a55 18
*) C++ and libpq++

I have not been able to build libpq++, the PostgreSQL C++ interface, with
the UnixWare or OpenServer C++ compilers.  By default, building PostgreSQL
also builds the libpq++ interface.  When that fails, it causes the entire
build of PostgreSQL to fail.

This is the problem if you see the following error message:

"pgenv.cc", line 47: error: no default constructor exists for class "string"

If you have this problem, you can disable building of libpq++ with the 
following configure option:

configure --without-CXX


***************************************************************************
a73 4
Putting this together with the no-C++ option above yields:

configure --with-libs=/usr/local/lib --with-includes=/usr/local/include --without-CXX

d79 1
a79 5
OpenServer, you need to use different arguments to the configure program.

First, you need to specify the "unixware" template instead of the default.

Second, you need to specify the locations of the UDK libraries.
d81 1
a81 1
Putting these together:
d83 1
a83 1
configure --with-template=unixware --with-libs=/udk/usr/lib --with-includes=/udk/usr/include
d85 1
a85 1
Putting these together with the no-C++ and readline options from above:
a86 1
./configure --with-template=unixware --with-libs="/udk/usr/lib /usr/local/lib" --with-includes="/udk/usr/include /usr/local/include" --without-CXX
d89 1
a89 1
*) Compiling PostgreSQL 7.0 with the UDK
d122 3
a124 3
The bind function in UnixWare 7.1+ has a problem when used with the AF_UNIX
family.  The following patch provides a work-around for the problem (thanks
go to Oliver PRENANT <ohp@@pyrenet.fre> for this patch).
a125 20
------------------------------8< CUT HERE >8------------------------------
*** src/backend/libpq/pqcomm.c.orig	Sun Oct  8 02:21:25 2000
--- src/backend/libpq/pqcomm.c	Sun Oct  8 02:42:57 2000
***************
*** 329,334 ****
--- 329,341 ----
  		return STATUS_ERROR;
  	}
  
+ 	/* Work around a bug in UnixWare 7.1.x - accept is not returning the
+ 	 * correct family when the family is AF_UNIX.
+ 	 */
+ 
+ 	if (port->raddr.sa.sa_family == 0)
+ 		port->raddr.sa.sa_family = AF_UNIX;
+ 
  	/* fill in the server (local) address */
  	addrlen = sizeof(port->laddr);
  	if (getsockname(port->sock, (struct sockaddr *) & port->laddr,
------------------------------8< CUT HERE >8------------------------------
a176 1

@


1.5
log
@Update platform FAQs
@
text
@d6 1
a6 1
last updated:           $Date$
d31 2
a32 2
You should locate your copy of the SCO Skunkware CD.  The Skunkware CD
is included with UnixWare 7 and current versions of OpenServer 5.
d38 2
a39 2
If you do not have this CD, the software on it
is available via anonymous ftp from ftp.sco.com/skunkware.
d43 3
a45 4
Skunkware has different versions for UnixWare and
OpenServer.  Make sure you install the correct version for your
operating system, except as noted below.

d50 3
a52 3
You need to use the GNU make program, which is on the Skunkware CD.
By default, it installs as /usr/local/bin/make.  To avoid confusion
with the SCO make program, you may want to rename GNU make to gmake.
d76 4
a79 5
If you install the readline library, then psql (the PostgreSQL command
line SQL interpreter) remembers each command you type, and allows
you to use arrow keys to recall and edit previous commands.  This is
very helpful, and is strongly recommended.  The readline library is
on the Skunkware CD.
d82 2
a83 2
you have the UnixWare 7.0.0 or 7.0.1 Skunkware CDs, you can install it
from there.  Otherwise, try ftp.sco.com/skunkware.
d87 2
a88 1
help.  If you installed readline, then use the following options to configure:
d119 1
a119 1
following version of the C compiler:
d121 2
a122 1
	Optimizing C Compilation System  (CCS) 3.2  08/18/98 (u701)
d128 2
a129 2
*** ./src/backend/utils/adt/int8.c.orig	Mon Apr  3 13:24:12 2000
--- ./src/backend/utils/adt/int8.c	Mon Apr  3 13:28:47 2000
d131 3
a133 3
*** 410,416 ****
  	if (*arg1 < 1)
  		*result = 0;
d135 2
a136 2
! 		for (i = *arg1, *result = 1; i > 0; --i)
  			*result *= i;
d138 4
a141 4
  	return result;
--- 410,416 ----
  	if (*arg1 < 1)
  		*result = 0;
d143 18
a160 2
! 		for (i = *arg1, *result = 1; 0 < i; --i)
  			*result *= i;
d162 10
a171 1
  	return result;
d178 2
a179 2
By default, UnixWare does not look there for man pages, so you will not
be able to read them.
@


1.4
log
@Update sco faq.
@
text
@d6 1
a6 1
last updated:           Mon May  1 23:35:43 EDT 2000
a24 2
*) Shared Memory and SHMMAX
*) Java and JDBC
a147 99

***************************************************************************
*) Shared Memory and SHMMAX

PostgreSQL supports multiple backend daemons running at once.  A block
of shared memory is used by the backend processes.  A larger block
of shared memory allows PostgreSQL to run faster and support more
complicated queries.

By default, UnixWare 7 and OpenServer are confiugured to support shared memory
blocks that are no larger than 524288 bytes, or 512K.  By default, PostgreSQL
tries to allocate a shared memory block that is larger than this.  If
you don't do anything, this allocation will fail, and the postmaster
daemon will not be able to run.

The error message looks like this (the numbers may be different):

IpcMemoryCreate: shmget failed (Invalid argument) key=5432001, size=831176, permission=600
FATAL 1:  ShmemCreate: cannot create region

You have two choices: tell PostgreSQL to allocate a smaller shared memory
block, or tell Unix to allow larger shared memory blocks.  The latter
is the preferred solution, but it requires a kernel tunable change and a 
reboot to implement.

To configure the size of the PostgreSQL shared memory block, use the -B
option to the postmaster command, which configures the number of buffers
used by PostgresSQL.  (The shared memory block consists of these buffers
and around 300K of other stuff.)  Each buffer uses 8K, and by default
there are 64 buffers, or 64*8*1024 = 524288 bytes (plus the ~300K of other
stuff).

To use PostgreSQL without doing any kernel tuning, use a -B value of 
about 24.  This would take up 24*8*1024 = 196608 bytes, plus ~300K
of other stuff, yields about 500000, which will fit in under the
default 512K limit.

Example: postmaster -B 24

The recommended option is to instead raise the kernel tunable SHMMAX, 
which controls the size of the largest allowed shared memory block.

*** Tuning SHMMAX on UnixWare ***

To display the current value of SHMMAX, run:
/etc/conf/bin/idtune -g SHMMAX
which displays the current, default, minimum, and maximum values, in bytes.

To set a new value for SHMMAX, run:
/etc/conf/bin/idtune SHMMAX value
where value is the new value you want to use (in bytes).

After setting SHMMAX, rebuild the kernel and reboot.
To rebuild the kernel:
/etc/conf/bin/idbuild -B

*** Tuning SHMMAX on OpenServer ***

First, cd to /etc/conf/cf.d.

To display the current value of SHMMAX, in bytes, run:
./configure -y SHMMAX

To set a new value for SHMMAX, run:
./configure SHMMAX=value
where value is the new value you want to use (in bytes).

After setting SHMMAX, rebuild the kernel and reboot.
To rebuild the kernel:
./link_unix


***************************************************************************
*) Java and JDBC

The JDBC interface will not build on UnixWare or OpenServer without changes.  
The JDBC Makefile in src/interfaces/jdbc/Makefile uses the $$( ) construction
to run an external shell command, instead of the older ` ` syntax.
However, the $$( ) syntax does not work on UnixWare or OpenServer.  
So, each of the two uses of it must be replaced with backquotes.  You can 
search for $$( to locate the two lines that need changing.

In the file src/interfaces/jdbc/Makefile :

change:
    make $$($(JAVA) makeVersion)
to:
    make `$(JAVA) makeVersion`

and change:
    $(JAR) -c0f $@@ $$($(FIND) postgresql -name "*.class" -print)
to:
    $(JAR) -c0f $@@ `$(FIND) postgresql -name "*.class" -print`

Of course, you also need to have installed Java on your system, and 
make sure that /usr/java/bin is in your PATH.

And, remember to use GNU make, as always.

@


1.3
log
@Update SCO FAQ. Billy G. Allie
@
text
@d283 2
a284 1
	sed -e '/^\.TH/s/"l"/"1sql"/' $i >../man.1sql/${i%.l}.1sql
@


1.2
log
@Update SCO FAQ>
@
text
@d6 1
a6 1
last updated:           Mon Apr 24 04:31:44 EDT 2000
d278 1
a278 1
mkdir ../man.1sql
d287 2
@


1.1
log
@FAQs contributed for this release.
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL  V6.5
d6 1
a6 1
last updated:           Tue May 25 12:00:00 PDT 1999
d8 1
a8 1
current maintainer:     Andrew Merrill (andrew@@compclass.com)
d12 1
a12 1
PostgreSQL 6.5 can be built on SCO UnixWare 7 and SCO OpenServer 5.
d24 1
d118 32
d257 4
a260 1
You need to make two changes to access the PostgreSQL man pages from UnixWare.
d262 1
a262 1
1) You need to modify the MANPATH environment variable.  I use:
d264 1
a264 2
MANPATH=/usr/local/pgsql/man:/usr/dt/man:/usr/man:/usr/share/man:scohelp
export MANPATH
d266 3
a268 2
2) The man pages for SQL commands are, by default, placed in section l
(normally used for "l"ocal pages).  UnixWare does not support the l section.
d270 3
a272 2
The solution I use is to move all these pages from section l to an unused
section, such as section 6.  To accomplish that:
d274 2
d277 5
a281 3
mv manl man6
cd man6
for file in *.l
d283 1
a283 1
	mv $file `basename $file .l`.6
d285 10
@
