mirror of
https://git.freebsd.org/ports.git
synced 2025-05-22 11:48:35 -04:00
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
87 lines
3.1 KiB
Text
87 lines
3.1 KiB
Text
|
|
Specific for updating 7.4.1->7.4.x:
|
|
|
|
A dump/restore is *not* required for those running 7.4, BUT:
|
|
|
|
If you want to install the fixes in the information schema you will
|
|
need to reload it into the database. This is either accomplished by
|
|
initializing a new cluster by running "initdb", or by running the
|
|
following sequence of SQL commands in each database (ideally including
|
|
template1) as a superuser in psql, after installing the new release:
|
|
|
|
DROP SCHEMA information_schema CASCADE;
|
|
\i %%PREFIX%%/pgsql/share/information_schema.sql
|
|
|
|
Fixes to the information schema (from HISTORY):
|
|
* Fix information schema for bit data types (Peter)
|
|
* Fix information schema view constraint_column_usage for foreign
|
|
keys (Peter)
|
|
|
|
=====================================================================
|
|
|
|
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.
|
|
|
|
You should vacuum and backup your database regularly. There is a
|
|
periodic script, %%PREFIX%%/etc/periodic/daily/502.pgsql, that you may
|
|
find useful. See the script for instructions.
|
|
|
|
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
|
|
|