summaryrefslogtreecommitdiff
path: root/databases/postgresql10-server/files (follow)
Commit message (Collapse)AuthorAgeFilesLines
* databases/postgresql10-server: fix build on riscv64Piotr Kubaj2021-12-201-20/+0
|
* databases/postgresql*: update to latest versionsPalle Girgensohn2021-08-121-254/+0
| | | | | | | | | | | | | | | | | The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 13.4, 12.8, 11.13, 10.18, and 9.6.23, as well as the third beta release of PostgreSQL 14. This release closes one security vulnerability and fixes over 75 bugs reported over the last three months. Turn off parallel builds since we continue to struggle with build problems when it is activated. [1] Avoid chasing latest LLVM version. [2] PR: 256466 [1], 256167 [2] Release notes: https://www.postgresql.org/docs/release/ Security: b471130b-fb86-11eb-87db-6cc21735f730
* databases/postgresql10-server: Fix typo in rc scriptLi-Wen Hsu2021-07-281-1/+1
| | | | | | PR: 257447 Reported by: Tom Warnke <tom@toromtomtom.com> MFH: 2021Q3
* 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/postgresql??-*: Upgrade to latest versionPalle Girgensohn2021-05-152-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/
* databases/postgresql*: Fix build on riscv64Loïc Bartoletti2021-04-201-0/+20
| | | | | Reported by: tmunro Reviewed by: girgen
* all: Remove all other $FreeBSD keywords.Mathieu Arnold2021-04-062-4/+0
|
* devel/icu: update to 68.1Jan Beich2020-11-031-0/+254
| | | | | | Changes: http://site.icu-project.org/download/68 ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/ Reported by: GitHub (watch releases)
* Convert to UCL & cleanup pkg-message (categories d)Mathieu Arnold2019-08-136-1/+36
|
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2019-05-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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]
* Update to latest versions of PostgreSQLPalle Girgensohn2018-02-082-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Recommand psycopg2 over PyGreSQLBaptiste Daroussin2017-10-151-1/+1
| | | | Submitted by: Christoph Moench-Tegeder <cmt@burggraben.net>
* Correct default data directory for postgresql 10Palle Girgensohn2017-09-241-2/+2
| | | | | | ...and make sure not to bump portrevision more than necessary. POINTED OUT BY: Peter Laursen
* Add PostgreSQL-10 to the ports treePalle Girgensohn2017-08-1016-0/+462
The PostgreSQL Global Development Group announces today that the third beta release of PostgreSQL 10 is available for download. This release contains previews of all of the features which will be available in the final release of version 10, including fixes to many of the issues found in the second beta. Users are encouraged to begin testing their applications against 10 beta3. URL: https://www.postgresql.org/about/news/1771/
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-09 07:32:29 +0000