summaryrefslogtreecommitdiff
path: root/databases/postgresql92-server/files/postgresql.in (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Update to latest versions of PostgreSQLPalle Girgensohn2018-02-081-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=461251
* PostgreSQL security updatesPalle Girgensohn2017-05-111-1/+1
| | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.3, 9.5.7, 9.4.12, 9.3.17, and 9.2.21. This release fixes three security issues. It also patches a number of other bugs reported over the last three months. Users who use the PGREQUIRESSL environment variable to control connections, and users who rely on security isolation between database users when using foreign servers, should update as soon as possible. Other users should plan to update at the next convenient downtime. URL: https://www.postgresql.org/about/news/1746/ Security: CVE-2017-7484, CVE-2017-7485, CVE-2017-7486 Also modify rcorder and let sshd start before PostgreSQL, so any problems during startup can be reviewed promplty from an ssh login. Notes: svn path=/head/; revision=440628
* Update PostgreSQL to latest versions.Palle Girgensohn2016-10-271-3/+3
| | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, and 9.1.24. This release fixes two issues that can cause data corruption, which are described in more detail below. It also patches a number of other bugs reported over the last three months. The project urges users to apply this update at the next possible downtime. Notes: svn path=/head/; revision=424765
* - Add profile support for PostgreSQL serversJason Helfman2012-01-221-2/+53
| | | | | | | | | | | | | | - re-assign LOCALBASE to PREFIX - add PG_GROUP to SUB_PLIST for packaging fix - fix permissions for package installations PR: ports/162776 Submitted by: jgh, Phil Phillips < pphillips at experts-exchange.com > Reviewed by: rene (mentor) Approved by: crees (maintainer, mentor) Notes: svn path=/head/; revision=289587
* In the rc.d scripts, change assignments to rcvar to use theDoug Barton2012-01-141-1/+1
| | | | | | | | | | | | | | literal name_enable wherever possible, and ${name}_enable when it's not, to prepare for the demise of set_rcvar(). In cases where I had to hand-edit unusual instances also modify formatting slightly to be more uniform (and in some cases, correct). This includes adding some $FreeBSD$ tags, and most importantly moving rcvar= to right after name= so it's clear that one is derived from the other. Notes: svn path=/head/; revision=289156
* Add postgresql 9.1 beta1.Palle Girgensohn2011-06-111-1/+1
| | | | | | | | | | | | | See http://www.postgresql.org/about/news.1313 for more info. Also, use USERS knob instead of explicitally creating the pgsql user while still accepting alternative names, using [1] with some added magic. PR: 157667 [1] Notes: svn path=/head/; revision=275407
* Update PostgreSQL to 9.0.4, 8.4.8, 8.3.15 and 8.2.21.Palle Girgensohn2011-04-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | This update contains a critical fix to the pg_upgrade utility which prevents significant downtime issues. Do not use pg_upgrade without installing this update first. The issue with pg_upgrade and the fix are detailed on the PostgreSQL wiki: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix Users who have already used pg_upgrade should run the database repair script given on that page on their databases as soon as possible. See the release notes for each version at http://www.postgresql.org/docs/current/static/release.html for a full list of changes with details. Allow the username of the postgresql user to configurable for 8.4 and 9.0. Largely inspired by the work of Jason Helfman [153668, 153136]. Change PGUSER knob to PG_USER not to clash with PGUSER environment. PR: 153668, 153136, 155493, 155137 Notes: svn path=/head/; revision=272900
* Begin the process of deprecating sysutils/rc_subr byDoug Barton2010-03-271-1/+1
| | | | | | | s#. %%RC_SUBR%%#. /etc/rc.subr# Notes: svn path=/head/; revision=251553
* Fix a few "bad example" problems in the rc.d scripts that have beenDoug Barton2009-07-151-3/+2
| | | | | | | | | | | | | | | | | | | | | | | propogated by copy and paste. 1. Primarily the "empty variable" default assignment, which is mostly ${name}_flags="", but fix a few others as well. 2. Where they are not already documented, add the existence of the _flags (or other deleted empties) option to the comments, and in some cases add comments from scratch. 3. Replace things that look like: prefix=%%PREFIX%% command=${prefix}/sbin/foo to just use %%PREFIX%%. In many cases the $prefix variable is only used once, and in some cases it is not used at all. 4. In a few cases remove ${name}_flags from command_args 5. Remove a long-stale comment about putting the port's rc.d script in /etc/rc.d (which is no longer necessary). No PORTREVISION bumps because all of these changes are noops. Notes: svn path=/head/; revision=237892
* Update postgresql to 8.2.1, 8.1.6, 8.0.10, 7.4.15 and 7.3.17.Palle Girgensohn2007-01-091-3/+3
| | | | | | | | | | | | | | | | | | | | | 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: svn path=/head/; revision=181869
* Welcome new release of the world's most advanced open source database:Palle Girgensohn2006-12-061-0/+64
PostgreSQL 8.2.0 Complete release notes are available at http://www.postgresql.org/docs/current/static/release-8-2.html Notes: svn path=/head/; revision=179046