From 6b11e898761ec7ced9bf9b652a24b78697eac863 Mon Sep 17 00:00:00 2001 From: Palle Girgensohn Date: Tue, 9 Jan 2007 16:29:35 +0000 Subject: Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17. Release notes: http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6 http://www.postgresql.org/docs/8.2/static/release-8-2-1.html The server-side utilities of postgresql (initdb, initlocation, ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now installed by the respective postgresql*-server port (previously they where installed with the client). If you update the client, you should also update the server to make sure you are not left without the server-side tools. Do something like: portupgrade postgresql-client postgresql-server --- .../files/pkg-message-server.in | 26 +++++++++++++--------- 1 file changed, 15 insertions(+), 11 deletions(-) (limited to 'databases/postgresql74-server/files/pkg-message-server.in') diff --git a/databases/postgresql74-server/files/pkg-message-server.in b/databases/postgresql74-server/files/pkg-message-server.in index 5378c0d7adfd..ac9e73b293f9 100644 --- a/databases/postgresql74-server/files/pkg-message-server.in +++ b/databases/postgresql74-server/files/pkg-message-server.in @@ -20,9 +20,7 @@ DROP SCHEMA information_schema CASCADE; ===================================================================== For procedural languages and postgresql functions, please note that -you might have to update them when updating the server. For example, -the "elog" method disappeared in postgresql-7.4, so postgresql-contrib -must be updated along with the server. +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 @@ -49,13 +47,19 @@ 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. -If you need to store any characters besides strict ASCII in your -database, you will want to set a character set, and possibly a -collation locale, before initializing the database. Add something -similar to this to /etc/login.conf: +Please note that if you use the rc script, +%%PREFIX%%/etc/rc.conf/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:\ - :setenv=LC_ALL=en_US.UTF-8,LC_COLLATE=C:\ + :lang=en_US.UTF-8:\ + :setenv=LC_COLLATE=C:\ :tc=default: --- and run `cap_mkdb /etc/login.conf'. @@ -65,15 +69,15 @@ Then add 'postgresql_class="postgres"' to /etc/rc.conf. To initialize the database, run - %%PREFIX%%/etc/rc.d/010.pgsql.sh initdb + %%PREFIX%%/etc/rc.d/postgresql initdb You can then start PostgreSQL by running: - %%PREFIX%%/etc/rc.d/010.pgsql.sh start + %%PREFIX%%/etc/rc.d/postgresql start For postmaster settings, see ~pgsql/data/postgresql.conf -NB. FreeBSD's PostgreSQL port now by default logs to syslog +NB. FreeBSD's PostgreSQL port logs to syslog by default See ~pgsql/data/postgresql.conf for more info ====================================================================== -- cgit v1.2.3