diff options
author | Palle Girgensohn <girgen@FreeBSD.org> | 2007-01-09 16:29:35 +0000 |
---|---|---|
committer | Palle Girgensohn <girgen@FreeBSD.org> | 2007-01-09 16:29:35 +0000 |
commit | 6b11e898761ec7ced9bf9b652a24b78697eac863 (patch) | |
tree | b375d70b112b334c43c9daa281851082f36a60da /databases/postgresql81-server/files/pkg-message-server.in | |
parent | Update to 2007.01.09. (diff) |
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
Notes
Notes:
svn path=/head/; revision=181869
Diffstat (limited to 'databases/postgresql81-server/files/pkg-message-server.in')
-rw-r--r-- | databases/postgresql81-server/files/pkg-message-server.in | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/databases/postgresql81-server/files/pkg-message-server.in b/databases/postgresql81-server/files/pkg-message-server.in index d22a731f40d8..cd6c42ed2090 100644 --- a/databases/postgresql81-server/files/pkg-message-server.in +++ b/databases/postgresql81-server/files/pkg-message-server.in @@ -30,13 +30,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'. |