aboutsummaryrefslogtreecommitdiff
path: root/databases/postgresql95-plpython
Commit message (Collapse)AuthorAgeFilesLines
* Welcome PostgreSQL 13Palle Girgensohn2020-09-241-1/+1
| | | | | | | 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-05-171-0/+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
* iThe PostgreSQL Global Development Group has released an update to allPalle Girgensohn2019-08-081-24/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Make sure we don't clobber slave ports' PORTREVISION.Mathieu Arnold2019-06-291-1/+2
| | | | Notes: svn path=/head/; revision=505361
* The PostgreSQL Global Development Group has released an update to allPalle Girgensohn2019-02-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-1/+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
* Update WWWSunpoet Po-Chuan Hsieh2018-05-081-1/+1
| | | | | | | Approved by: portmgr (blanket) Notes: svn path=/head/; revision=469407
* Correct default data directory for postgresql 10Palle Girgensohn2017-09-241-0/+1
| | | | | | | | | ...and make sure not to bump portrevision more than necessary. POINTED OUT BY: Peter Laursen Notes: svn path=/head/; revision=450532
* Fix the PostgreSQL 10 package names.Mathieu Arnold2017-08-171-1/+1
| | | | | | | | | | Most of them were called things like postgresql10beta3-docs-10.b3 With hat: portmgr Sponsored by: Absolight Notes: svn path=/head/; revision=448138
* Add more PLIST_SUB to Mk/Uses/python.mkSunpoet Po-Chuan Hsieh2017-01-071-6/+0
| | | | | | | | | | | | | | | | | | | - 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 Notes: svn path=/head/; revision=430839
* Delete the now expired postgresql90 ports. Upstream support forMatthew Seaman2016-07-012-2/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | postgresql-9.0.x was declared EoL in September 2015. Summary: Remove 9.0 from the list of postgresql versions available in ports Disconnect postgresql90 ports from the build Remove postgresql90-pgtcl port Remove postgresql90-client port Move the master postgreslXY-plperl makefile to postgresql95-plperl/Makefile. Adjust include lines in other postgresqlXY-plperl ports Delete postgresql90-plperl Move the master postgreslXY-plpython/{Makefile,pkg-descr} to postgresl95-plpython/{Makefile,pkg-descr} Adjust all other postgresqlXY-plpython/Makefile to include the new master Remove postgresql90-server Reviewers: jgh, girgen, #portmgr, O5 Ports Framework, bapt, crees Reviewed By: #portmgr, O5 Ports Framework, bapt, crees Subscribers: mat Differential Revision: https://reviews.freebsd.org/D6898 Notes: svn path=/head/; revision=417899
* The PostgreSQL Global Development Group announces thePalle Girgensohn2016-01-071-0/+5
release of PostgreSQL 9.5. This release adds UPSERT capability, Row Level Security, and multiple Big Data features, which will broaden the user base for the world's most advanced database. With these new capabilities, PostgreSQL will be the best choice for even more applications for startups, large corporations, and government agencies. Release Notes: http://www.postgresql.org/docs/current/static/release-9-5.html What's New in 9.5: https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.5 Notes: svn path=/head/; revision=405482
generated by cgit v1.3 (git 2.53.0) at 2026-09-02 00:17:04 +0000