ports/databases/postgresql72/files/post-install-notes
Sean Chittenden d87a4a6578 Bow to the masses who have complained bitterly about not being able to
upgrade to the PostgreSQL 7.3 series and provide an update to the 7.2
series, 7.2.4.  :~]  This port _will_ be removed and should EOL'ed in
about 6 months time.  Since there is no future for these bits, ignore their
heritage commit an orphan for the 7 series.  See the postgresql7 port for
future and past bits.  This port is only intended to serve as a means of
postponing an inevitable upgrade to recent release.

DBAs, please plan and begin upgrading to 7.3.X, the grass really is greener.

Release notes:
http://developer.postgresql.org/docs/postgres/release-7-2-4.html

PR:		ports/48025
Submitted by:	Palle Girgensohn <girgen@pingpong.net>
2003-02-07 11:00:47 +00:00

57 lines
1.8 KiB
Text

The PostgreSQL port has a collection of "side orders":
postgresql-doc
For all of the html documentation
p5-Pg
A perl5 API for client access to PostgreSQL databases.
postgresql-tcltk
If you want tcl/tk client support. You get a neat GUI, pgaccess, as
a bonus!
postgresql-jdbc
For Java JDBC support.
postgresql-odbc
For client access from unix applications using ODBC as access
method. Not needed to access unix PostgreSQL servers from Win32
using ODBC. See below.
ruby-postgres, py-PyGreSQL
For client access to PostgreSQL databases using the ruby & python
languages.
postgresql-plperl, postgresql-pltcl & postgresql-plruby
For using perl5, tcl & ruby as procedural languages.
etc etc...
Note that many files have moved around compared to previous versions
of PostgreSQL. For example, plpgsql.so and all other language modules
are now in /usr/local/lib/postgresql.
If you have many tables and many clients running, consider raising
kern.maxfiles using sysctl(8), or reconfigure your kernel
appropriately.
You should vacuum and backup your database regularly. There is a
periodic script, /usr/local/share/postgresql/502.pgsql, that you may
find useful.
To allow many simultaneous connections to your PostgreSQL server, you
should raise the SystemV shared memory limits in your kernel. Here are
example values for allowing up to 180 clients (tinkering in
postgresql.conf also needed, of course):
options SYSVSHM
options SYSVSEM
options SYSVMSG
options SHMMAXPGS=65536
options SEMMNI=40
options SEMMNS=240
options SEMUME=40
options SEMMNU=120
If you plan to access your PostgreSQL server using ODBC, please
consider running the SQL script /usr/local/share/postgresql/odbc.sql
to get the functions required for ODBC compliance.