summaryrefslogtreecommitdiff
path: root/databases/postgresql93-server (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove expired ports:Rene Ladan2019-01-0927-2855/+0
| | | | | | | | | | | 2019-01-08 databases/postgresql93-client: PostgreSQL-9.3 has reached end-of-life 2019-01-08 databases/postgresql93-docs: PostgreSQL-9.3 has reached end-of-life 2019-01-08 databases/postgresql93-contrib: PostgreSQL-9.3 has reached end-of-life 2019-01-08 databases/postgresql93-pltcl: PostgreSQL-9.3 has reached end-of-life databases/postgresql93-pgtcl: part of expired PostgreSQL 9.3 2019-01-08 databases/postgresql93-plperl: PostgreSQL-9.3 has reached end-of-life 2019-01-08 databases/postgresql93-plpython: PostgreSQL-9.3 has reached end-of-life 2019-01-08 databases/postgresql93-server: PostgreSQL-9.3 has reached end-of-life
* Bump PORTREVISION for ports depending on the canonical version of GCCGerald Pfeifer2018-12-121-0/+1
| | | | | | | | | | | | | | | defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t GCC 8.2 under most circumstances. This includes ports - with USE_GCC=yes or USE_GCC=any, - with USES=fortran, - using Mk/bsd.octave.mk which in turn features USES=fortran, and - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang, c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib plus, as a double check, everything INDEX-11 showed depending on lang/gcc7. PR: 231590
* Posted on 2018-11-08 by PostgreSQL Global Development Group The PostgreSQLPalle Girgensohn2018-11-082-5/+5
| | | | | | | | | | | | | | | | | | | | | Global Development Group has released an update to all supported versions of our database system, including 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25. This release fixes one security issue as well as bugs reported over the last three months. 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 if you are using pg_stat_statements in your installation. This update is also the final release for PostgreSQL 9.3, which is now end-of-life and will no longer receive any bug or security fixes. If your environment still uses PostgreSQL 9.3, please make plans to update to a community supported version as soon as possible. Please see our versioning policy for more information. Releasenotes: https://www.postgresql.org/about/news/1905/ Security: 1c27a706-e3aa-11e8-b77a-6cc21735f730 Security: CVE-2018-16850
* PostgreSQL-9.3 has reached end-of-lifePalle Girgensohn2018-11-081-0/+2
| | | | Please upgrade to a later version
* The PostgreSQL Global Development Group has released an update to all supportedPalle Girgensohn2018-08-103-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | versions of our database system, including 10.5, 9.6.10, 9.5.14, 9.4.19, 9.3.24. This release fixes two security issues as well as bugs reported over the last three months. If you have untrusted users accessing your system and you are either running PostgreSQL 9.5 or a newer version OR have installed the "dblink" or "postgres_fdw" extensions, you must apply this update as soon as possible. All other users can upgrade at the next convenient downtime. Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.5 from any 10.x release is considered a minor update. The PostgreSQL Global Development Group also announces that the third beta release of PostgreSQL 11 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 11 (though some details of the release could change before then) as well as bug fixes that were reported during the second beta. This release also changes the default option for the server packages to *not* include XML support per default. If you need this, please check the XML option knob and build the port. Releasenotes: https://www.postgresql.org/about/news/1878/ PR: 229523, 198588 Security: 96eab874-9c79-11e8-b34b-6cc21735f730 Security: CVE-2018-10915, CVE-2018-10925
* UpPalle Girgensohn2018-05-112-4/+4
| | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.4, 9.6.9, 9.5.13, 9.4.18, 9.3.23. This release fixes one security issue as well as several bugs reported over the last three months. Users should plan to update at the next convenient downtime. Please see the "Updating" section for post-installation steps for the security fix and the "incorrect volatility and parallel-safety markings" fix. Releasenotes: https://www.postgresql.org/about/news/1851/ Security: CVE-2018-1115 Too-permissive access control list on function pg_logfile_rotate() FreeBSD's port of PostgreSQL uses syslog by default, so the above security problem is only a problem if you changed the logging configuration. Please visit the releasenotes linked above and take the actions needed.
* Update WWWSunpoet Po-Chuan Hsieh2018-05-081-1/+1
| | | | Approved by: portmgr (blanket)
* 2018-03-01 Security Update ReleasePalle Girgensohn2018-03-013-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of the PostgreSQL database system, including 10.3, 9.6.8, 9.5.12, 9.4.17, and 9.3.22. The purpose of this release is to address CVE-2018-1058, which describes how a user can create like-named objects in different schemas that can change the behavior of other users' queries and cause unexpected or malicious behavior, also known as a "trojan-horse" attack. Most of this release centers around added documentation that describes the issue and how to take steps to mitigate the impact on PostgreSQL databases. We strongly encourage all of our users to please visit https://wiki.postgresql.org/wiki/A_Guide_to_CVE-2018-1058:_Protect_Your_Search_Path for a detailed explanation of CVE-2018-1058 and how to protect your PostgreSQL installations. After evaluating the documentation for CVE-2018-1058, a database administrator may need to take follow up steps on their PostgreSQL installations to ensure they are protected from exploitation. Security: CVE-2018-1058
* Update to latest versions of PostgreSQLPalle Girgensohn2018-02-085-9/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Update to latest versions of PostgreSQLPalle Girgensohn2017-11-093-5/+4
| | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 10.1, 9.6.6, 9.5.10, 9.4.15, 9.3.20, and 9.2.24. This release fixes three security issues. This release also fixes issues found in BRIN indexing, logical replication and other bugs reported over the past three months. Please note that the CVE-2017-12172 does not affect the FreeBSD port unless you decided to not use the contrib/startscript instead of the startscript distributed with the FreeBSD port/package. Security: CVE-2017-12172, CVE-2017-15099, CVE-2017-15098 URL: https://www.postgresql.org/about/news/1801/
* Recommand psycopg2 over PyGreSQLBaptiste Daroussin2017-10-151-1/+1
| | | | Submitted by: Christoph Moench-Tegeder <cmt@burggraben.net>
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2017-09-052-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | supported versions of our database system, including 9.6.5, 9.5.9, 9.4.14, 9.3.19, and 9.2.23. This release includes fixes that prevent a crash in pg_restore when using parallel mode. It also patches over a few other bugs reported since the last releases in August. Additionally, in 9.4.14 only, there is a fix to an issue with walsenders preventing primary-server shutdown unless immediate shutdown mode is used. Users should plan to update at the next convenient downtime. Bug Fixes and Improvements This update also fixes a number of bugs reported in the last few weeks. Some of these issues affect only version 9.6, but many affect all supported versions: * Show foreign tables in information_schema.table_privileges view. This fix applies to new databases, see the release notes for the procedure to apply the fix to an existing database. * Correctly identify columns that are of a range type or domain type over a composite type or domain type being searched for * Prevent crash when passing fixed-length pass-by-reference data types to parallel worker processes * Change ecpg’s parser to allow RETURNING clauses without attached C variables * Change ecpg’s parser to recognize backslash continuation of C preprocessor command lines * Improve selection of compiler flags for PL/Perl on Windows
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2017-08-102-4/+4
| | | | | | | | | | | | | | supported versions of our database system, including 9.6.4, 9.5.8, 9.4.13, 9.3.18, and 9.2.22. This release fixes three security issues. It also patches over 50 other bugs reported over the last three months. Users who are affected by the below security issues should update as soon as possible. Users affected by CVE-2017-7547 (https://access.redhat.com/security/cve/CVE-2017-7547) will need to perform additional steps after upgrading to resolve the issue. Other users should plan to update at the next convenient downtime. URL: https://www.postgresql.org/about/news/1772/ Security: CVE-2017-7546, CVE-2017-7547, CVE-2017-7548
* - Include pg_regress to all postgresql*-client ports, to allow running ↵Dmitry Marakasov2017-07-171-0/+1
| | | | | | | regression tests for postgresql extensions PR: 217874 Approved by: maintainer timeout (pgsql, 4 months)
* PostgreSQL security updatesPalle Girgensohn2017-05-114-5/+6
| | | | | | | | | | | | | | | | | 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.
* PostgreSQL 9.6.2, 9.5.6, 9.4.11, 9.3.16 and 9.2.20 released!Palle Girgensohn2017-02-093-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.2, 9.5.6, 9.4.11, 9.3.16, and 9.2.20. This release includes fixes that prevent data corruption issues in index builds and in certain write-ahead-log replay situations, which are detailed below. It also patches over 75 other bugs reported over the last three months. Users should plan to apply this update at the next scheduled downtime. Build corruption with CREATE INDEX CONCURRENTLY There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been indexed incorrectly. If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update. This issue is present in the 9.2, 9.3, 9.4, 9.5, and 9.6 series of PostgreSQL. URL https://www.postgresql.org/about/news/1733/
* Add more PLIST_SUB to Mk/Uses/python.mkSunpoet Po-Chuan Hsieh2017-01-071-5/+5
| | | | | | | | | | | | | | | | - Add PYTHON_PYOEXTENSION and PYTHON_SUFFIX - Add PYTHON2 and PYTHON3 - Respect PYTHON_VERSION - Rename PYOEXTENSION to PYTHON_PYOEXTENSION This change would help: - Build databases/postgresql*-plpython with Python 3 (It has PLIST issue since bsd.python.mk to Uses/python.mk transition) - Simplify Makefile PR: 205807 Differential Revision: https://reviews.FreeBSD.org/D4758 Exp-run by: antoine
* Update PostgreSQL to latest versions.Palle Girgensohn2016-10-275-10/+10
| | | | | | | | | | | 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.
* - fix sizesOlli Hauer2016-08-111-1/+1
| | | | | | - s/USE_OPENSSL/USES=ssl/ assumed OK for commit ~1h after first notify about wrong sizes in distinfo
* The PostgreSQL Global Development Group has released an update to all supportedPalle Girgensohn2016-08-113-6/+9
| | | | | | | | | | | | | | | versions of our database system, including 9.5.4, 9.4.9, 9.3.14, 9.2.18 and 9.1.23. This release fixes two security issues. It also patches a number of other bugs reported over the last three months. Users who rely on security isolation between database users should update as soon as possible. Other users should plan to update at the next convenient downtime. If you are using the ICU patch, please consult UPDATING. Improve periodic cleanup, suggested by claudius (at) ambtec.de. [1] PR: 210941 [1] Security: CVE-2016-5423, CVE-2016-5424
* Rename all files containing a : in their filename.Mathieu Arnold2016-06-171-0/+0
| | | | | | | While there, run make makepatch on affected ports, and rename patches accordingly. Sponsored by: Absolight
* - Fix trailing whitespace in pkg-messagesDmitry Marakasov2016-05-191-1/+1
| | | | Approved by: portmgr blanket
* Update PostgreSQL to latest versionsPalle Girgensohn2016-05-123-3/+5
| | | | URL: http://www.postgresql.org/docs/9.5/static/release-9-5-3.html
* Update PostgreSQL 9.1, 9.2 9.3 and 9.4 to latest versions.Palle Girgensohn2016-03-313-3/+6
| | | | URL: http://www.postgresql.org/about/news/1656/
* Update PostgreSQL to latest versions.Palle Girgensohn2016-02-134-44/+46
| | | | | | | | | | | | | | | | | Security Fixes for Regular Expressions, PL/Java This release closes security hole CVE-2016-0773, an issue with regular expression (regex) parsing. Prior code allowed users to pass in expressions which included out-of-range Unicode characters, triggering a backend crash. This issue is critical for PostgreSQL systems with untrusted users or which generate regexes based on user input. The update also fixes CVE-2016-0766, a privilege escalation issue for users of PL/Java. Certain custom configuration settings (GUCS) for PL/Java will now be modifiable only by the database superuser URL: http://www.postgresql.org/about/news/1644/ Security: CVE-2016-0773, CVE-2016-0766
* Update PostgreSQL port to latest version.Palle Girgensohn2015-10-083-3/+4
| | | | | | | | | | | | | | | | | | | | Two security issues have been fixed in this release which affect users of specific PostgreSQL features: CVE-2015-5289: json or jsonb input values constructed from arbitrary user input can crash the PostgreSQL server and cause a denial of service. CVE-2015-5288: The crypt( function included with the optional pgCrypto extension could be exploited to read a few additional bytes of memory. No working exploit for this issue has been developed. This update will also disable SSL renegotiation by default; previously, it was enabled by default. SSL renegotiation will be removed entirely in PostgreSQL versions 9.5 and later. URL: http://www.postgresql.org/about/news/1615/ Security: CVE-2015-5288 CVE-2015-5289
* Fix broken XML support.Palle Girgensohn2015-10-061-1/+0
| | | | PR: ports/202649
* Simplify a bit the MakefilesBaptiste Daroussin2015-07-222-158/+158
| | | | | Use OPTIONS_SUB to automatically PLIST_SUB Use OPTIONS helpers
* Cleanup plist and avoid useless @execBaptiste Daroussin2015-07-227-97/+2
|
* Update PostgreSQL to latest versions.Palle Girgensohn2015-06-122-3/+3
| | | | | | | | | | Earlier update releases attempted to fix an issue in PostgreSQL 9.3 and 9.4 with "multixact wraparound", but failed to account for issues doing multixact cleanup during crash recovery. This could cause servers to be unable to restart after a crash. As such, all users of 9.3 and 9.4 should apply this update as soon as possible. URL: http://www.postgresql.org/about/news/1592/
* Update PostgreSQL to latest versions.Palle Girgensohn2015-06-052-3/+3
| | | | | | | The update is mostly to fix the file persmission problem described in the URL below. You might want to wait until next upgrade, depending on you local configuration. URL: http://www.postgresql.org/about/news/1590/
* Update PostgreSQL ports to latest version.Palle Girgensohn2015-05-223-3/+6
| | | | | | | | | | | | | | | Data Corruption Fix For users of PostgreSQL versions 9.3 or 9.4, this release fixes a problem where the database will fail to protect against "multixact wraparound", resulting in data corruption or loss. Users with a high transaction rate (1 million or more per hour) in a database with many foreign keys are especially vulnerable. We strongly urge all users of 9.4 and 9.3 to update their installations in the next few days. Users of versions 9.2 and earlier are not affected by this issue. Security: fc38cd83-00b3-11e5-8ebd-0026551a22dc
* Chase upcoming update of ICU to 5.5.Palle Girgensohn2015-04-181-2/+2
|
* remove redundant cpe markers on the slave portsPalle Girgensohn2015-04-051-2/+0
|
* databases/postgresql93-server: add CPE informationBartek Rutkowski2015-03-201-0/+2
| | | | | | | - Maintainer's timeout (pgsql@FreeBSD.org) PR: 197488 Submitted by: Shun <shun.fbsd.pr@dropcut.net>
* Update PostgreSQL-9.x to latests versions.Palle Girgensohn2015-02-058-857/+861
| | | | | | | | | | | This update fixes multiple security issues reported in PostgreSQL over the past few months. All of these issues require prior authentication, and some require additional conditions, and as such are not considered generally urgent. However, users should examine the list of security holes patched below in case they are particularly vulnerable. Security: CVE-2015-0241,CVE-2015-0242,CVE-2015-0243, CVE-2015-0244,CVE-2014-8161
* - Unbreak builds after the lang/python27 update (r363790)Marcus von Appen2014-08-021-11/+0
| | | | Exp-run: 192242, 192244
* Update to the latest snapshots.Chris Rees2014-07-304-109/+99
| | | | | | | | uuid-ossp patch has been outdated with irrelevant changes (for us), so massage back in. In head of postgresql, this is handled properly, so eventually the ossp patches can go.
* In preparation for upcoming ICU-5.3 upgrade, I failed to update distfile on ↵Palle Girgensohn2014-06-121-2/+2
| | | | slave ports
* Fix mistake with ossp-uuid: don't use --with-ossp-uuid, since it will needPalle Girgensohn2014-03-211-0/+10
| | | | the ossp library present, and then we never use it.
* The PostgreSQL Global Development Group has released an update to all supportedPalle Girgensohn2014-03-204-7/+406
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | version of the database system, including versions 9.3.4, 9.2.8, 9.1.13, 9.0.17, and 8.4.21. This minor release fixes a data corruption issue with replication and crash recovery in version 9.3, as well as several other minor issues in all versions. All users of version 9.3 are urged to update their installations at the next possible downtime. Users of older versions should update at their convenience. The data corruption issue in PostgreSQL 9.3 affects binary replication standbys, servers being recovered from point-in-time-recovery backup, and standalone servers which recover from a system crash. The bug causes unrecoverable index corruption during recovery due to incorrect replay of row locking operations. This can then cause query results to be inconsistent depending on whether or not an index is used, and eventually lead to primary key violations and similar issues. For this reason, users are encouraged to replace each of their standby databases with a new base backup after applying the update. See release notes for more changes. URL: http://www.postgresql.org/docs/current/static/release.html URL: https://wiki.postgresql.org/wiki/20140320UpdateIssues A change specific to the FreeBSD port: Modify the contrib/uuid-ossp to actually work (not crashing the backend) by using the libc implementation of uuid instead of the ossp port. Schemas and queries will just work. Based on the work of Andrew Gierth. 9.1+ EXTENSION support added by girgen@. URL: http://pgfoundry.org/projects/uuid-freebsd PR: ports/121745, ports/182846
* Stage supportAntoine Brodin2014-02-262-15/+256
| | | | | Reviewed by: postgresql@ Tested by: miwi and me
* The PostgreSQL Global Development Group has released an importantPalle Girgensohn2014-02-204-16/+9
| | | | | | | | | | | | | | | | | | | | | | update to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.3, 9.2.7, 9.1.12, 9.0.16, and 8.4.20. This update contains fixes for multiple security issues, as well as several fixes for replication and data integrity issues. All users are urged to update their installations at the earliest opportunity, especially those using binary replication or running a high-security application. This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management. Before this fix, any member of a ROLE was able to grant others access to the same ROLE regardless if the member was given the WITH ADMIN OPTION permission. It also fixes multiple privilege escalation issues, including: CVE-2014-0061, CVE-2014-0062, CVE-2014-0063, CVE-2014-0064, CVE-2014-0065, and CVE-2014-0066. More information on these issues can be found on our security page and the security issue detail wiki page. Security: CVE-2014-0060,CVE-2014-0061,CVE-2014-0062,CVE-2014-0063 CVE-2014-0064,CVE-2014-0065,CVE-2014-0066,CVE-2014-0067
* fix messed up file sizes for icu patchPalle Girgensohn2014-02-101-1/+1
|
* Chase ICU updatePalle Girgensohn2014-02-101-2/+2
|
* The PostgreSQL Global Development Group has released a critical updatePalle Girgensohn2013-12-052-3/+3
| | | | | | | | | | to all supported versions of the PostgreSQL database system, which includes minor versions 9.3.2, 9.2.6, 9.1.11, 9.0.15, and 8.4.19. This update fixes three serious data-loss bugs affecting replication and database maintenance. All users are urged to update their installations at the earliest opportunity. URL: http://www.postgresql.org/about/news/1492/
* - Fix PLIST for python3Sunpoet Po-Chuan Hsieh2013-10-281-7/+8
| | | | | Submitted by: sunpoet (myself) Approved by: crees (pgsql)
* - Remove DISTV: only used in PKGNAMESUFFIX and complained by portlintSunpoet Po-Chuan Hsieh2013-10-151-2/+1
| | | | | | | | - Convert to new LIB_DEPENDS format for postgresql*-contrib Submitted by: sunpoet (myself) Reviewed by: crees (pgsql) Approved by: jgh (pgsql)
* Update PostgreSQL ports to 9.3.1, 9.2.5, 9.1.10, 9.0.14, and 8.4.18.Palle Girgensohn2013-10-124-5/+7
| | | | | | | | Note that users of the hstore extension on version 9.3 must take an additional, post upgrade step of running "ALTER EXTENSION hstore UPDATE" in each database after update. URL: http://www.postgresql.org/about/news/1487/
* - Fix pkg name collisionJason Helfman2013-10-101-1/+2
| | | | | Reviewed by: pgsql@ With hat: pgsql@
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-18 00:38:08 +0000