non port: databases/postgresql10-server/pkg-plist-client |
SVNWeb
|
Number of commits found: 10 |
Tue, 7 Mar 2023
|
[ 21:40 Rene Ladan (rene) ] 3839b19 (Only the first 10 of 36 ports in this commit are shown above. )
databases/postgresql10-*: Remove expired ports
2023-03-07 databases/postgresql10-client: PostgreSQL 10 has reached end-of-life
2023-03-07 databases/postgresql10-contrib: PostgreSQL 10 has reached end-of-life
2023-03-07 databases/postgresql10-docs: PostgreSQL 10 has reached end-of-life
2023-03-07 databases/postgresql10-pgtcl: PostgreSQL-10 has reached end-of-life
2023-03-07 databases/postgresql10-plperl: PostgreSQL 10 has reached end-of-life
2023-03-07 databases/postgresql10-plpython: PostgreSQL 10 has reached
end-of-life
2023-03-07 databases/postgresql10-pltcl: PostgreSQL 10 has reached end-of-life
2023-03-07 databases/postgresql10-server: PostgreSQL 10 has reached end-of-life
|
Thu, 19 May 2022
|
[ 13:36 Palle Girgensohn (girgen) ] 5b11f47 (Only the first 10 of 54 ports in this commit are shown above. )
databases/postgresql??-*: add postgresql-15 to the ports tree
Introduce PostgreSQL-15 to the ports tree.
Make version 15 the master port, and add plist parameter for the
postgresql version.
Release notes: https://www.postgresql.org/docs/devel/release.html
|
Thu, 13 Aug 2020
|
[ 13:45 girgen ] (Only the first 10 of 14 ports in this commit are shown above. )
The PostgreSQL Global Development Group has released an update to all
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. (Only the first 15 lines of the commit message are shown above )
|
Fri, 15 Feb 2019
|
[ 11:02 girgen ] (Only the first 10 of 34 ports in this commit are shown above. )
The PostgreSQL Global Development Group has released an update to all
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 (Only the first 15 lines of the commit message are shown above )
|
Fri, 10 Aug 2018
|
[ 09:25 girgen ] (Only the first 10 of 20 ports in this commit are shown above. )
The PostgreSQL Global Development Group has released an update to all supported
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 (Only the first 15 lines of the commit message are shown above )
|
Fri, 11 May 2018
|
[ 13:10 girgen ] (Only the first 10 of 14 ports in this commit are shown above. )
Up
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.
|
Thu, 1 Mar 2018
|
[ 15:10 girgen ] (Only the first 10 of 16 ports in this commit are shown above. )
2018-03-01 Security Update Release
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
|
Thu, 8 Feb 2018
|
[ 17:38 girgen ] (Only the first 10 of 31 ports in this commit are shown above. )
Update to latest versions of PostgreSQL
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.
(Only the first 15 lines of the commit message are shown above )
|
Thu, 21 Sep 2017
|
[ 13:43 girgen ]
Upgrading to RC 1
PostgreSQL 10 RC 1 requires an upgrade from beta 4, or earlier either
using pg_dump / pg_restore or pg_upgrade.
Any bug fixes applied to 9.6 or earlier that also affected 10 are
included in RC 1, as well issues that were reported with Beta 4.
Changes Since Beta 4
PostgreSQL 10 RC 1 contains fixes for issues discovered by users when
testing Beta 4, including:
* Add psql variables showing server version and psql version.
* Several fixes for partitioning
* Several fixes for logical replication
* Several fixes for transition tables
* Fix for query that could end up in an uninterruptible state
Note that some known issues remain unfixed. Before reporting a bug in
the release candidate, please check the Open Items page.
URL: https://wiki.postgresql.org/wiki/New_in_postgres_10
URL: https://www.postgresql.org/docs/devel/static/release-10.html
|
Thu, 10 Aug 2017
|
[ 14:23 girgen ] (Only the first 10 of 22 ports in this commit are shown above. )
Add PostgreSQL-10 to the ports tree
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/
|
Number of commits found: 10 |