From d841eb94b16fac58b307b35f0c2849842e5eea54 Mon Sep 17 00:00:00 2001
From: Rene Ladan <rene@FreeBSD.org>
Date: Fri, 24 Jul 2020 17:01:38 +0000
Subject: Remove expired ports:

2020-07-24 databases/postgresql94-client: PostgreSQL-9.4 has reached end-of-life
2020-07-24 databases/postgresql94-contrib: PostgreSQL-9.4 has reached end-of-life
2020-07-24 databases/postgresql94-docs: PostgreSQL-9.4 has reached end-of-life
2020-07-24 databases/postgresql94-pgtcl: PostgreSQL-9.4 has reached end-of-life
2020-07-24 databases/postgresql94-plpython: PostgreSQL-9.4 has reached end-of-life
2020-07-24 databases/postgresql94-server: PostgreSQL-9.4 has reached end-of-life
2020-07-24 databases/postgresql94-pltcl: PostgreSQL-9.4 has reached end-of-life
2020-07-24 databases/postgresql94-plperl: PostgreSQL-9.4 has reached end-of-life
---
 .../files/pkg-message-server.in                    | 69 ----------------------
 1 file changed, 69 deletions(-)
 delete mode 100644 databases/postgresql94-server/files/pkg-message-server.in

(limited to 'databases/postgresql94-server/files/pkg-message-server.in')

diff --git a/databases/postgresql94-server/files/pkg-message-server.in b/databases/postgresql94-server/files/pkg-message-server.in
deleted file mode 100644
index 84a13f7cb47c..000000000000
--- a/databases/postgresql94-server/files/pkg-message-server.in
+++ /dev/null
@@ -1,69 +0,0 @@
-[
-{ type: install
-  message: <<EOM
-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 perform vacuum on all
-databases nightly. Per default, it performs `vacuum analyze'. See the
-script for instructions. For autovacuum settings, please review
-~pgsql/data/postgresql.conf.
-
-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
-
-NB. If you're not using a checksumming filesystem like ZFS, you might
-    wish to enable data checksumming. It can only be enabled during
-    the initdb phase, by adding the "--data-checksums" flag to
-    the postgres_initdb_flags rcvar.  Check the initdb(1) manpage
-    for more info and make sure you understand the performance
-    implications.
-
-======================================================================
-
-To run PostgreSQL at startup, add
-'postgresql_enable="YES"' to /etc/rc.conf
-EOM
-}
-]
-- 
cgit v1.2.3