955b7d13bc
2018-02-08 Security Update Release ================================== The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.2, 9.6.7, 9.5.11, 9.4.16, 9.3.21. This release fixes two security issues. This release also fixes issues with VACUUM, GIN indexes, and hash indexes that could lead to data corruption, as well as fixes for using parallel queries and logical replication. All users using the affected versions of PostgreSQL should update as soon as possible. Please see the notes on "Updating" below for any post-update steps that may be required. Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.2 from 10.0 or 10.1 is considered a minor update. Security Issues --------------- Two security vulnerabilities have been fixed by this release: * CVE-2018-1052: Fix the processing of partition keys containing multiple expressions * CVE-2018-1053: Ensure that all temporary files made with "pg_upgrade" are non-world-readable Local fixes to the FreeBSD ports -------------------------------- Inform users about data checksums [1]. Make sure /usr/bin/su is used regardless of PATH settings [2]. Enable DTRACE by default [3]. PR: 214671 [1], 223157 [2], 215028 [3] Security: c602c791-0cf4-11e8-a2ec-6cc21735f730
64 lines
2.4 KiB
Text
64 lines
2.4 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 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
|
|
|