head	1.1;
access;
symbols
	HORDE_1_2_7:1.1.2.2
	HORDE_1_2_6:1.1.2.2
	HORDE_1_2_5:1.1.2.2
	HORDE_1_2_4:1.1.2.1
	HORDE_1_2_3:1.1.2.1
	HORDE_1_2_2:1.1.2.1
	HORDE_1_2_1:1.1.2.1
	HORDE_1_2_0:1.1.2.1
	HORDE_1_2_0_pre14:1.1.2.1
	HORDE_1_2_0_pre13:1.1.2.1
	STABLE_1_2:1.1.0.2;
locks; strict;
comment	@# @;


1.1
date	2000.04.09.20.34.56;	author chuck;	state dead;
branches
	1.1.2.1;
next	;

1.1.2.1
date	2000.04.09.20.34.56;	author chuck;	state Exp;
branches;
next	1.1.2.2;

1.1.2.2
date	2001.02.04.03.52.09;	author rich;	state Exp;
branches;
next	;


desc
@@


1.1
log
@file POSTGRESQL was initially added on branch STABLE_1_2.
@
text
@@


1.1.2.1
log
@database README files and setup scripts for supported platforms. phplib
pieces coming soon for oracle, ifmx, and sybase
@
text
@a0 11
Due to the fact that I can't tell if you have made any changes to your
PostgreSQL server let alone what the password is for it you will have to
configure the PostgreSQL server by hand.

There is a file called pgsql_create.sql in this directory
(horde/scripts/database) that all you have to do is import that into your
PostgreSQL database.

If you make changes to the name of the database, the manager name or
password, you will need to make the same changes to your
imp/config/defaults.php3 file as well.
@


1.1.2.2
log
@Inform PostgreSQL users that they should VACUUM and VACUUM ANALYZE
regularly.
@
text
@d7 1
a7 1
PostgreSQL database (with the "\i" command).
a11 4

The active_sessions table sees a lot of inserts and deletes; be sure
to VACUUM and VACUUM ANALYZE at least that table regularly. See
the PostgreSQL user's guide for further information on VACUUM.
@


