ade1c57e3a
PostgreSQL 16.3, 15.7, 14.12, 13.15, and 12.19 Released! The PostgreSQL Global Development Group has released an update to all supported versions of PostgreSQL, including 16.3, 15.7, 14.12, 13.15, and 12.19. This release fixes one security vulnerability and over 55 bugs reported over the last several months. Please note that the fix in this release for CVE-2024-4317 only fixes fresh PostgreSQL installations, namely those that are created with the initdb utility after this fix is applied. If you have a current PostgreSQL installation and are concerned about this issue, please follow the additional updating instructions provided in the CVE-2024-4317 description or the release notes for the remediation. [1] The script is installed as /usr/local/share/postgresql/fix-CVE-2024-4317.sql PostgreSQL 12 will stop receiving fixes on November 14, 2024. If you are running PostgreSQL 12 in a production environment, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information. [1]: https://www.postgresql.org/support/security/CVE-2024-4317/ Security: d53c30c1-0d7b-11ef-ba02-6cc21735f730 PR: 277428 (remove unneded patch) PR: 260494 (remove deprecated INTDATE option) PR: 265860 (correct path for contrib README file in pkg-message)
84 lines
3.0 KiB
Plaintext
84 lines
3.0 KiB
Plaintext
[
|
|
{ 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
|
|
~%%PG_USER%%/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:
|
|
---
|
|
%%PG_USER%%:\
|
|
:lang=en_US.UTF-8:\
|
|
:setenv=LC_COLLATE=C:\
|
|
:tc=default:
|
|
---
|
|
and run `cap_mkdb /etc/login.conf'.
|
|
Then add 'postgresql_login_class="%%PG_USER%%"' to /etc/rc.conf, or
|
|
set it as the %%PG_USER%% user's login class in /etc/passwd.
|
|
|
|
======================================================================
|
|
|
|
To use PostgreSQL, enable it in rc.conf using
|
|
|
|
sysrc postgresql_enable=yes
|
|
|
|
To initialize the database, run
|
|
|
|
service postgresql initdb
|
|
|
|
You can then start PostgreSQL by running:
|
|
|
|
service postgresql start
|
|
|
|
For postmaster settings, see ~%%PG_USER%%/data/postgresql.conf
|
|
|
|
NB. FreeBSD's PostgreSQL port logs to syslog by default
|
|
See ~%%PG_USER%%/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 be enabled during
|
|
the initdb phase, by adding the "--data-checksums" flag to
|
|
the postgresql_initdb_flags rcvar. Otherwise you can enable it later by
|
|
using pg_checksums. Check the initdb(1) manpage for more info
|
|
and make sure you understand the performance implications.
|
|
|
|
======================================================================
|
|
|
|
SECURITY ADVICE
|
|
|
|
If upgradring from a version 16.x < 16.3
|
|
A security vulnerability was found in the system views pg_stats_ext
|
|
and pg_stats_ext_exprs, potentially allowing authenticated database
|
|
users to see data they shouldn't. If this is of concern in your
|
|
installation, run the SQL script %%DATADIR%%/fix-CVE-2024-4317.sql
|
|
for each of your databases. For details, see
|
|
https://www.postgresql.org/support/security/CVE-2024-4317/
|
|
|
|
|
|
EOM
|
|
}
|
|
]
|