aboutsummaryrefslogtreecommitdiff
path: root/databases/postgresql96-server/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* Fix up PORTREVISION style after "portedit bump-revision"Jan Beich2020-03-131-1/+1
| | | | Notes: svn path=/head/; revision=528344
* devel/icu: update to 66.1Jan Beich2020-03-131-1/+1
| | | | | | | | Changes: http://site.icu-project.org/download/66 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ Notes: svn path=/head/; revision=528343
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2020-02-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | supported versions of our database system, including 12.2, 11.7, 10.12, 9.6.17, 9.5.21, and 9.4.26. This release fixes one security issue found in the PostgreSQL server and over 75 bugs reported over the last three months. Users should plan to update as soon as possible. PostgreSQL 9.4 Now EOL This is the last release for PostgreSQL 9.4, which will no longer receive security updates and bug fixes. PostgreSQL 9.4 introduced new features such as JSONB support, the `ALTER SYSTEM` command, the ability to stream logical changes to an output plugin, and more: https://www.postgresql.org/about/news/1557/ https://www.postgresql.org/docs/9.4/release-9-4.html While we are very proud of this release, these features are also found in newer versions of PostgreSQL. Many of these features have also received improvements, and, per our versioning policy, it is time to retire PostgreSQL 9.4. To receive continued support, we suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see the PostgreSQL versioning policy for more information. Security Issues * CVE-2020-1720: `ALTER ... DEPENDS ON EXTENSION` is missing authorization checks. Versions Affected: 9.6 - 12 The `ALTER ... DEPENDS ON EXTENSION` sub-commands do not perform authorization checks, which can allow an unprivileged user to drop any function, procedure, materialized view, index, or trigger under certain conditions. This attack is possible if an administrator has installed an extension and an unprivileged user can `CREATE`, or an extension owner either executes `DROP EXTENSION` predictably or can be convinced to execute `DROP EXTENSION`. Release notes: https://www.postgresql.org/docs/current/release.html Notes: svn path=/head/; revision=526063
* Upgrade PostgreSQLPalle Girgensohn2019-11-141-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 12.1, 11.6, 10.11, 9.6.16, 9.5.20, and 9.4.25. This release fixes over 50 bugs reported over the last three months. PostgreSQL 9.4 will stop receiving fixes on February 13, 2020, which is the next planned cumulative update release. We suggest that you make plans to upgrade to a newer, supported version of PostgreSQL. Please see our versioning policy for more information: This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions. Specific change to the FreeBSD port: Starting now, the default for TZDATA has changed to using the underlying OS' time zone database instead of the one built in to PostgreSQL. This change is made since PostgreSQL will not release a patch in the event where the time zone database changes, whereas FreeBSD will. Release notes: https://www.postgresql.org/about/news/1994/ URL: https://www.postgresql.org/support/versioning/ Notes: svn path=/head/; revision=517600
* devel/icu: update to 65.1Jan Beich2019-10-031-1/+1
| | | | | | | | Changes: http://site.icu-project.org/download/65 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ Notes: svn path=/head/; revision=513733
* iThe PostgreSQL Global Development Group has released an update to allPalle Girgensohn2019-08-081-7/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | supported versions of our database system, including 11.5, 10.10, 9.6.15, 9.5.19, and 9.4.24, as well as the third beta of PostgreSQL 12. This release fixes two security issues in the PostgreSQL server, two security issues found in one of the PostgreSQL Windows installers, and over 40 bugs reported since the previous release. Users should install these updates as soon as possible. A Note on the PostgreSQL 12 Beta ================================ In the spirit of the open source PostgreSQL community, we strongly encourage you to test the new features of PostgreSQL 12 in your database systems to help us eliminate any bugs or other issues that may exist. While we do not advise you to run PostgreSQL 12 Beta 3 in your production environments, we encourage you to find ways to run your typical application workloads against this beta release. Your testing and feedback will help the community ensure that the PostgreSQL 12 release upholds our standards of providing a stable, reliable release of the world's most advanced open source relational database. Security Issues =============== Two security vulnerabilities have been closed by this release: * CVE-2019-10208: `TYPE` in `pg_temp` executes arbitrary SQL during `SECURITY DEFINER` execution Versions Affected: 9.4 - 11 Given a suitable `SECURITY DEFINER` function, an attacker can execute arbitrary SQL under the identity of the function owner. An attack requires `EXECUTE` permission on the function, which must itself contain a function call having inexact argument type match. For example, `length('foo'::varchar)` and `length('foo')` are inexact, while `length('foo'::text)` is exact. As part of exploiting this vulnerability, the attacker uses `CREATE DOMAIN` to create a type in a `pg_temp` schema. The attack pattern and fix are similar to that for CVE-2007-2138. Writing `SECURITY DEFINER` functions continues to require following the considerations noted in the documentation: https://www.postgresql.org/docs/devel/sql-createfunction.html#SQL-CREATEFUNCTION-SECURITY The PostgreSQL project thanks Tom Lane for reporting this problem. * CVE-2019-10209: Memory disclosure in cross-type comparison for hashed subplan Versions Affected: 11 In a database containing hypothetical, user-defined hash equality operators, an attacker could read arbitrary bytes of server memory. For an attack to become possible, a superuser would need to create unusual operators. It is possible for operators not purpose-crafted for attack to have the properties that enable an attack, but we are not aware of specific examples. The PostgreSQL project thanks Andreas Seltenreich for reporting this problem. Notes: svn path=/head/; revision=508390
* Bump PORTREVISION for ports depending on the canonical version of GCCGerald Pfeifer2019-07-261-1/+1
| | | | | | | | | | | | | | | | | | as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3 to GCC 9.1 under most circumstances now after revision 507371. 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, everything INDEX-11 shows with a dependency on lang/gcc9 now. PR: 238330 Notes: svn path=/head/; revision=507372
* Upgrade PostgreSQL to latest versionPalle Girgensohn2019-06-271-1/+1
| | | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 11.4, 10.9, 9.6.14, 9.5.18, and 9.4.23, as well as the second beta of PostgreSQL 12. This release fixes one security issue and over 25 bugs since the previous cumulative update in May. This release is made outside of the normal update release schedule as the security vulnerability was determined to be critical enough to distribute the fix as quickly as possible. Users who are running PostgreSQL 10, PostgreSQL 11, or the PostgreSQL 12 beta should upgrade as soon as possible. All other users should plan to apply this update at the next scheduled downtime. Release notes: https://www.postgresql.org/about/news/1949/ Security: 245629d4-991e-11e9-82aa-6cc21735f730 Notes: svn path=/head/; revision=505245
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2019-05-091-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | supported versions of our database system, including 11.3, 10.8, 9.6.13, 9.5.17, and 9.4.22. This release fixes two security issues in the PostgreSQL server, a security issue found in two of the PostgreSQL Windows installers, and over 60 bugs reported over the last three months. Security: CVE-2019-10129: Memory disclosure in partition routing Prior to this release, a user running PostgreSQL 11 can read arbitrary bytes of server memory by executing a purpose-crafted INSERT statement to a partitioned table. Security: CVE-2019-10130: Selectivity estimators bypass row security policies PostgreSQL maintains statistics for tables by sampling data available in columns; this data is consulted during the query planning process. Prior to this release, a user able to execute SQL queries with permissions to read a given column could craft a leaky operator that could read whatever data had been sampled from that column. If this happened to include values from rows that the user is forbidden to see by a row security policy, the user could effectively bypass the policy. This is fixed by only allowing a non-leakproof operator to use this data if there are no relevant row security policies for the table. This issue is present in PostgreSQL 9.5, 9.6, 10, and 11. The PostgreSQL project thanks Dean Rasheed for reporting this problem. Also fix a FreeBSD port problem with LLVM [1] and add promote command to `service postgresql` [2] PR: 236100, 234879 Submitted by: tomonori.usaka@ubin.jp [1], Trix Farrar [2] Notes: svn path=/head/; revision=501149
* Don't overwrite PORTREVISION from the slave, following readline update.Chris Rees2019-04-251-1/+1
| | | | | | | | | | | | | I've had to bump revision for several slaves here, but most will not be rebuilt, except the -client slaves. Apologies for anyone having to rebuild -clients unnecessarily, but it's not a heavy task- better safe than sorry. PR: ports/236156 Reported by: Andrew Dunstan (PostgreSQL), koobs, Dmitri Goutnik Notes: svn path=/head/; revision=500060
* devel/icu: update to 64.1Jan Beich2019-03-271-1/+1
| | | | | | | | | | | Changes: http://site.icu-project.org/download/64 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ PR: 236325 Exp-run by: antoine Differential Revision: https://reviews.freebsd.org/D19479 Notes: svn path=/head/; revision=496981
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2019-02-151-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | supported versions of our database system, including 11.2, 10.7, 9.6.12, 9.5.16, and 9.4.21. This release changes the behavior in how PostgreSQL interfaces with `fsync()` and includes fixes for partitioning and over 70 other bugs that were reported over the past three months. Users should plan to apply this update at the next scheduled downtime. FreeBSD port adds OPTIONS knob to support LLVM JIT. [1] Highlight: Change in behavior with fsync() ------------------------------------------ When available in an operating system and enabled in the configuration file (which it is by default), PostgreSQL uses the kernel function `fsync()` to help ensure that data is written to a disk. In some operating systems that provide `fsync()`, when the kernel is unable to write out the data, it returns a failure and flushes the data that was supposed to be written from its data buffers. This flushing operation has an unfortunate side-effect for PostgreSQL: if PostgreSQL tries again to write the data to disk by again calling `fsync()`, `fsync()` will report back that it succeeded, but the data that PostgreSQL believed to be saved to the disk would not actually be written. This presents a possible data corruption scenario. This update modifies how PostgreSQL handles a `fsync()` failure: PostgreSQL will no longer retry calling `fsync()` but instead will panic. In this case, PostgreSQL can then replay the data from the write-ahead log (WAL) to help ensure the data is written. While this may appear to be a suboptimal solution, there are presently few alternatives and, based on reports, the problem case occurs extremely rarely. A new server parameter `data_sync_retry` has been added to manage this behavior. If you are certain that your kernel does not discard dirty data buffers in such scenarios, you can set `data_sync_retry` to `on` to restore the old behavior. Release Notes: https://www.postgresql.org/about/news/1920/ PR: 232490 [1] Notes: svn path=/head/; revision=492989
* 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 Notes: svn path=/head/; revision=487272
* Posted on 2018-11-08 by PostgreSQL Global Development Group The PostgreSQLPalle Girgensohn2018-11-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=484488
* The PostgreSQL Global Development Group has released an update to all supportedPalle Girgensohn2018-08-101-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=476819
* devel/icu: update to 62.1Jan Beich2018-06-291-1/+1
| | | | | | | | | | Changes: http://site.icu-project.org/download/62 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ PR: 229359 Exp-run by: antoine (only 10.4) Notes: svn path=/head/; revision=473551
* UpPalle Girgensohn2018-05-111-2/+2
| | | | | | | | | | | | | | | | | | | | 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. Notes: svn path=/head/; revision=469638
* devel/icu: update to 61.1Jan Beich2018-04-061-1/+1
| | | | | | | | | | | Changes: http://site.icu-project.org/download/61 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ PR: 227042 Exp-run by: antoine MFH: 2018Q2 (required by Firefox 61) Notes: svn path=/head/; revision=466648
* 2018-03-01 Security Update ReleasePalle Girgensohn2018-03-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=463327
* Update to latest versions of PostgreSQLPalle Girgensohn2018-02-081-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Update to latest versions of PostgreSQLPalle Girgensohn2017-11-091-2/+2
| | | | | | | | | | | | | | | | | | 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/ Notes: svn path=/head/; revision=453847
* devel/icu: update to 60.1Jan Beich2017-11-091-1/+1
| | | | | | | | | | Changes: http://site.icu-project.org/download/60 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ PR: 223373 Exp-run by: antoine Notes: svn path=/head/; revision=453790
* devel/icu: update to 59.1Jan Beich2017-09-251-1/+1
| | | | | | | | | | | | - Temporarily keep C++98 working in consumers for Clang's default -std= Changes: http://site.icu-project.org/download/59 PR: 218788 Submitted by: takefu@airport.fm, dcarmich@dcarmichael.net (early version) Exp-run by: antoine Notes: svn path=/head/; revision=450556
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2017-09-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=449278
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2017-08-101-1/+1
| | | | | | | | | | | | | | | | | 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 Notes: svn path=/head/; revision=447678
* - Add missing file to plistDmitry Marakasov2017-07-171-0/+1
| | | | | | | | PR: 217874 Approved by: maintainer timeout (postgres, 2 weeks) Notes: svn path=/head/; revision=446064
* 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
* PostgreSQL 9.6.2, 9.5.6, 9.4.11, 9.3.16 and 9.2.20 released!Palle Girgensohn2017-02-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/ Notes: svn path=/head/; revision=433738
* Update PostgreSQL to latest versions.Palle Girgensohn2016-10-271-2/+2
| | | | | | | | | | | | | | 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
* PostgreSQL 9.6, the latest version of the world's leading open sourcePalle Girgensohn2016-09-291-2/+1
| | | | | | | | | | | | database, was released today by the PostgreSQL Global Development Group. This release will allow users to both scale up and scale out high performance database workloads. New features include parallel query, synchronous replication improvements, phrase search, and improvements to performance and usability, as well as many more features. Notes: svn path=/head/; revision=422916
* - Update devel/icu to 57.1.Tijl Coosemans2016-09-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - Clean up the Makefile. - Follow some upstream recommendations (--with-data-packaging=archive, --disable-renaming, -DICU_NO_USER_DATA_OVERRIDE). - Patch makefiles to install static libraries with INSTALL_DATA so they aren't stripped. - Patch config/mh-bsd-gcc to sync with config/mh-linux-gcc. - Fix endianness detection in ICU. The code wanted to use BYTE_ORDER defined in machine/endian.h, but this isn't visible because ICU is compiled with _XOPEN_SOURCE. Patch the code to use _BYTE_ORDER instead. - Compile ICU with C++11 compiler to enable move constructors. - Patch ICU to fix a problem with atomics in the case of a C++11 compiler without C++11 header <atomic> (like Clang on FreeBSD 9). - Bump all ports that depend on it due to library version change. - Add USES=compiler:c++0x to some ports that pick up -std=c++0x from ICU pkgconfig files. - Add USES=compiler:c++11-lib to graphics/libcdr01 because it also needs a C++11 runtime library now. Add this to all ports that depend on it so their executables load the right libstdc++.so on FreeBSD 9. PR: 205120 Exp-run by: antoine Approved by: portmgr (antoine) Notes: svn path=/head/; revision=422711
* We should tell initdb which user we want as DBAPalle Girgensohn2016-09-211-1/+1
| | | | Notes: svn path=/head/; revision=422551
* Fix plist problem for postgresql-9.6 [1]Palle Girgensohn2016-09-071-1/+1
| | | | | | | | | | Fix spelling while here [2] Pointed out by: matthew [1], bcr [2] Pointy hat to: girgen Notes: svn path=/head/; revision=421475
* Fix broken package name for PostgreSQL 9.6 RC1Palle Girgensohn2016-09-051-1/+1
| | | | | | | Fix bad pkg-plist for postgresql 9.6 server Notes: svn path=/head/; revision=421361
* Add PostgreSQL-9.6 RC1Palle Girgensohn2016-09-051-0/+26
Please read the entry from 20160905 in UPDATING: daemon user has changed to `postgres' ICU is default on Notes: svn path=/head/; revision=421360
generated by cgit v1.2.3 (git 2.25.1) at 2025-03-06 21:37:58 +0000