aboutsummaryrefslogtreecommitdiff
path: root/databases/postgresql12-server/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* databases/postgresql??-server: rc-script should require DAEMONPalle Girgensohn2021-06-011-1/+1
| | | | | | | | | | Changeset ab83f2b4bb78 changed the startup order for Postgresql. The cleartmp rc.d now comes after the Postgresql startup. Unfortunately, Postgresql likes to create a socket in /tmp/.s.PGSQL.5432. After cleartmp does its work, that socket disappears from the filesystem. Submitted by: Jeroen Pulles PR: 256335
* databases/postgresql14-*: Add postgresql 14 beta1 the the ports tree.Palle Girgensohn2021-05-201-1/+1
| | | | | | | | | Release notes: https://www.postgresql.org/docs/devel/release-14.html Also reintroduce parallel builds. Some components, namely plperl, plpython, pltcl and contrib, fail to build properly when using parallel builds. Something with static linking using `ar` that fails. MAKE_JOBS_UNSAFE is set for these ports.
* databases/postgresql??-*: Upgrade to latest versionPalle Girgensohn2021-05-151-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PostgreSQL 13.3, 12.7, 11.12, 10.17, and 9.6.22 Released! The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.3, 12.7, 11.12, 10.17, and 9.6.22. This release closes three security vulnerabilities and fixes over 45 bugs reported over the last three months. Security fixes in this release: CVE-2021-32027: Buffer overrun from integer overflow in array subscripting calculations CVE-2021-32028: Memory disclosure in INSERT ... ON CONFLICT ... DO UPDATE CVE-2021-32029: Memory disclosure in partitioned-table UPDATE ... RETURNING Also plenty of bug fixes. See the release note for details. Changes to the port: Make sure we use the matching version of llvm. This fixes a problem with the llvm version string not being monotonically increasing with the version number. [1] Better pkg message about checksums for postgresql 12+. [2] [4] Adjust login class parameter to adhere to the documentation in rc.subr(8) [3]: The rc.conf parameter for the login class of the postgresql daemon has changed name from postgresql_class to postgresql_login_class, since rc.subr(8) states that the parameter should be named ${name}_login_class. Allow parallel builds. [5] Correct the directory name for the user postgres in pkg message. [6] PR: 250824 [1], 253558 [2], 236060 [3], 233106 [4], 230656 [5] PR: 226674 [6] Submitted by: Michael Zhilin [2], Michael Zhilin [3], Dmitry Chestnykh [4] Submitted by: Steve Wills [5], knezour [6] Security: 76e0bb86-b4cb-11eb-b9c9-6cc21735f730 Security: 62da9702-b4cc-11eb-b9c9-6cc21735f730 Release notes: https://www.postgresql.org/docs/release/
* devel/icu: update to 69.1Jan Beich2021-04-081-1/+1
| | | | | Changes: https://github.com/unicode-org/icu/releases/tag/release-69-1 Reported by: GitHub (watch releases)
* Remove # $FreeBSD$ from Makefiles.Mathieu Arnold2021-04-061-1/+0
|
* PostgreSQL 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25 releasedPalle Girgensohn2021-02-111-1/+1
| | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25. This release closes two security vulnerabilities and fixes over 80 bugs reported over the last three months. Additionally, this is the final release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade. Release notes: https://www.postgresql.org/about/news/postgresql-132-126-1111-1016-9621-and-9525-released-2165/ Security notes: https://www.postgresql.org/support/security/ Security: CVE-2021-3393, CVE-2021-20229 Notes: svn path=/head/; revision=564956
* PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20 released!Palle Girgensohn2020-11-121-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.1, 12.5, 11.10, 10.15 and 9.6.20. This release closes three security vulnerabilities and fixes over 65 bugs reported over the last three months. Due to the nature of CVE-2020-25695, we advise you to update as soon as possible. Additionally, this is the second-to-last release of PostgreSQL 9.5. If you are running PostgreSQL 9.5 in a production environment, we suggest that you make plans to upgrade. For the full list of changes, please review the release notes. Security: CVE-2020-25695: Multiple features escape "security restricted operation" sandbox Security: CVE-2020-25694: Reconnection can downgrade connection security settings Security: CVE-2020-25696: psql's \gset allows overwriting specially treated variables Notes: svn path=/head/; revision=554966
* devel/icu: update to 68.1Jan Beich2020-11-031-1/+1
| | | | | | | | | Changes: http://site.icu-project.org/download/68 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ Reported by: GitHub (watch releases) Notes: svn path=/head/; revision=553940
* Try to fix build on recent FreeBSD versions where clang version > llvm defaultPalle Girgensohn2020-09-301-1/+1
| | | | | | | | | | | | | | | | | ports version. Fix this by depending on a higher version of llvm if such a version exixts, and otherwise use a clang version compatible with the latest llvm. Using llvm was previously dependant on clang being used, and this did not quite work for all cases due to some weird order of variables in the Makefile. The result was that the option set by the used was not really honored. The portrevision is bumped to reflect that the setting of LLVM might not have worked before this portrevison. PR: 244403 Notes: svn path=/head/; revision=550749
* Welcome PostgreSQL 13Palle Girgensohn2020-09-241-296/+4
| | | | | | | Release notes: https://www.postgresql.org/about/news/2077/ Notes: svn path=/head/; revision=549921
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2020-08-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | supported versions of our database system, including 12.4, 11.9, 10.14, 9.6.19, and 9.5.23. This release closes two security vulnerabilities and fixes over 50 bugs reported over the last three months. Please plan to update at your earliest convenience. Security Issues --------------- * CVE-2020-14349: Uncontrolled search path element in logical replication. Versions Affected: 10 - 12. The PostgreSQL `search_path` setting determines schemas searched for tables, functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided client applications to sanitize `search_path`, but logical replication continued to leave `search_path` unchanged. Users of a replication publisher or subscriber database can create objects in the `public` schema and harness them to execute arbitrary SQL functions under the identity running replication, often a superuser. Installations having adopted a documented secure schema usage pattern are not vulnerable. The PostgreSQL project thanks Noah Misch for reporting this problem. * CVE-2020-14350: Uncontrolled search path element in `CREATE EXTENSION`. Versions Affected: 9.5 - 12. The security team typically does not test unsupported versions, but this problem is quite old. When a superuser runs certain `CREATE EXTENSION` statements, users may be able to execute arbitrary SQL functions under the identity of that superuser. The attacker must have permission to create objects in the new extension's schema or a schema of a prerequisite extension. Not all extensions are vulnerable. In addition to correcting the extensions provided with PostgreSQL, the PostgreSQL Global Development Group is issuing guidance for third-party extension authors to secure their own work. The PostgreSQL project thanks Andres Freund for reporting this problem. Security: CVE-2020-14349, CVE-2020-14350 Notes: svn path=/head/; revision=544810
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2020-05-171-3/+2
| | | | | | | | | | | | | | | | | | | | supported versions of our database system, including 12.3, 11.8, 10.13, 9.6.18, and 9.5.22. This release fixes one security issue found in the PostgreSQL server and over 75 bugs reported over the last three months. Please plan to update at your earliest convenience. Update the backup warning text. [1] Add plpython and plperl libs for hstore, jsonb and ltree for the versions where they exist. These libs are added to the postgresql??-plpython and -plperl ports, inspired by [2]. PR: 237910 [1], 245246 [2] Submitted by: Francesco [1], Loïc Bartoletti [2] Notes: svn path=/head/; revision=535676
* devel/icu: update to 67.1Jan Beich2020-04-231-1/+1
| | | | | | | | | Changes: http://site.icu-project.org/download/67 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ Reported by: GitHub (watch releases) Notes: svn path=/head/; revision=532707
* 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
* databases/postgresql12-server: fix build on GCC architecturesPiotr Kubaj2020-03-061-1/+4
| | | | | | | | | | | Use LLVM only if Clang is used. PR: 244225 Approved by: pgsql (maintainer timeout) MFH: 2020Q1 (fix build blanket) Notes: svn path=/head/; revision=527871
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2020-02-131-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Fix PLIST problems when building with LLVM but without GSSAPI or OPENSSL.Palle Girgensohn2019-10-171-0/+8
| | | | | | | | PR: 241053, 241166 Submitted by: Artyom Davidov Notes: svn path=/head/; revision=514661
* Upgrade to postgresql-12.0Palle Girgensohn2019-10-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | PostgreSQL 12 enhancements include notable improvements to query performance, particularly over larger data sets, and overall space utilization. This release provides application developers with new capabilities such as SQL/JSON path expression support, optimizations for how common table expression ("WITH") queries are executed, and generated columns. The PostgreSQL community continues to support the extensibility and robustness of PostgreSQL, with further additions to internationalization, authentication, and providing easier ways to administrate PostgreSQL. This release also introduces the pluggable table storage interface, which allows developers to create their own methods for storing data. "The development community behind PostgreSQL contributed features for PostgreSQL 12 that offer performance and space management gains that our users can achieve with minimal effort, as well as improvements in enterprise authentication, administration functionality, and SQL/JSON support." said Dave Page, a core team member of the PostgreSQL Global Development Group. "This release continues the trend of making it easier to manage database workloads large and small while building on PostgreSQL's reputation of flexibility, reliability and stability in production environments." Release notes: https://www.postgresql.org/about/news/1976/ Notes: svn path=/head/; revision=513665
* Upgrade PostgreSQL-12 to rc1Palle Girgensohn2019-09-271-2/+2
| | | | | | | | | | | | | | | | | | | | There have been many bug fixes for PostgreSQL 12 reported during the Beta 4 period and applied to this release candidate. These include: Add additional "leakproof" markings to certain string functions to better support nondeterministic collations. This can positively impact the performance of some query plans Removal of the ECPG DECLARE STATEMENT functionality The ecpglib major version change was reverted Fix handling of nondeterministic collations with pattern_ops opclasses Release notes: https://www.postgresql.org/about/news/1975/ Notes: svn path=/head/; revision=513024
* Switch default devel/llvm* to 90Jan Beich2019-09-201-1/+1
| | | | | | | | | PR: 239682 Reviewed by: tobik Differential Revision: https://reviews.freebsd.org/D21172 Notes: svn path=/head/; revision=512440
* Fix typo in rc.d scriptPalle Girgensohn2019-09-171-1/+1
| | | | | | | | | | The data directory was badly named data11 instead of the more correct data12. PR: 239798 Submitted by: Dmitry Wagin Notes: svn path=/head/; revision=512199
* Update to PostgreSQL-12b4Palle Girgensohn2019-09-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group announces that the fourth beta release of PostgreSQL 12 is now available for download. This release contains previews of all features that will be available in the final release of PostgreSQL 12, though some details of the release could change before then. This is likely the final beta release of PostgreSQL 12 before a release candidate is made available. 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. Upgrading to PostgreSQL 12 Beta 4 To upgrade to PostgreSQL 12 Beta 4 from Beta 3 or an earlier version of PostgreSQL 12, you will need to use a strategy similar to upgrading between major versions of PostgreSQL (e.g. `pg_upgrade` or `pg_dump` / `pg_restore`). For more information, please visit the documentation section on upgrading: https://www.postgresql.org/docs/12/static/upgrading.html URL: https://wiki.postgresql.org/wiki/PostgreSQL_12_Open_Items#resolved_before_12beta4 Notes: svn path=/head/; revision=511971
* iThe PostgreSQL Global Development Group has released an update to allPalle Girgensohn2019-08-081-0/+308
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
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-29 08:19:43 +0000