978e3de48f
http://www.postgresql.org/docs/current/static/release-8-3-5.html http://www.postgresql.org/docs/current/static/release-8-2-11.html http://www.postgresql.org/docs/current/static/release-8-1-15.html http://www.postgresql.org/docs/current/static/release-8-0-19.html http://www.postgresql.org/docs/current/static/release-7-4-23.html Note that the GiST problem mentioned does not apply to users of the FreeBSD port, since the previous version of PostgreSQL never reached the ports tree, due to the freeze of the tree pending the FreeBSD 7.1 update. PR: 121848, 124713
70 lines
2.5 KiB
Text
70 lines
2.5 KiB
Text
For procedural languages and postgresql functions, please note that
|
|
you might have to update them when updating the server.
|
|
|
|
If you have many tables and many clients running, consider raising
|
|
kern.maxfiles using sysctl(8), or reconfigure your kernel
|
|
appropriately.
|
|
|
|
The port is set up to use autovacuum for new databases, but you might
|
|
also want to vacuum and perhaps backup your database regularly. There
|
|
is a periodic script, %%PREFIX%%/etc/periodic/daily/502.pgsql, that
|
|
you may find useful. You can use it to backup and perfom vacuum on all
|
|
databases nightly. Per default, it perfoms `vacuum analyze'. See the
|
|
script for instructions. For autovacuum settings, please review
|
|
~pgsql/data/postgresql.conf.
|
|
|
|
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 (configurations 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 %%PREFIX%%/share/postgresql/odbc.sql
|
|
to get the functions required for ODBC compliance.
|
|
|
|
Please note that if you use the rc script,
|
|
%%PREFIX%%/etc/rc.d/postgresql, to initialize the database, unicode
|
|
(UTF-8) will be used to store character data by default. Set
|
|
postgresql_initdb_flags or use login.conf settings described below to
|
|
alter this behaviour. See the start rc script for more info.
|
|
|
|
To set limits, environment stuff like locale and collation and other
|
|
things, you can set up a class in /etc/login.conf before initializing
|
|
the database. Add something similar to this to /etc/login.conf:
|
|
---
|
|
postgres:\
|
|
:lang=en_US.UTF-8:\
|
|
:setenv=LC_COLLATE=C:\
|
|
:tc=default:
|
|
---
|
|
and run `cap_mkdb /etc/login.conf'.
|
|
Then add 'postgresql_class="postgres"' to /etc/rc.conf.
|
|
|
|
======================================================================
|
|
|
|
To initialize the database, run
|
|
|
|
%%PREFIX%%/etc/rc.d/postgresql initdb
|
|
|
|
You can then start PostgreSQL by running:
|
|
|
|
%%PREFIX%%/etc/rc.d/postgresql start
|
|
|
|
For postmaster settings, see ~pgsql/data/postgresql.conf
|
|
|
|
NB. FreeBSD's PostgreSQL port logs to syslog by default
|
|
See ~pgsql/data/postgresql.conf for more info
|
|
|
|
======================================================================
|
|
|
|
To run PostgreSQL at startup, add
|
|
'postgresql_enable="YES"' to /etc/rc.conf
|
|
|