notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Want a good monitor light? See my photosAll times are UTC
Ukraine
This referral link gives you 10% off a Fastmail.com account and gives me a discount on my Fastmail account.

Get notified when packages are built

A new feature has been added. FreshPorts already tracks package built by the FreeBSD project. This information is displayed on each port page. You can now get an email when FreshPorts notices a new package is available for something on one of your watch lists. However, you must opt into that. Click on Report Subscriptions on the right, and New Package Notification box, and click on Update.

Finally, under Watch Lists, click on ABI Package Subscriptions to select your ABI (e.g. FreeBSD:14:amd64) & package set (latest/quarterly) combination for a given watch list. This is what FreshPorts will look for.

non port: databases/postgresql96-server/pkg-plist-server

Number of commits found: 14

Friday, 11 Mar 2022
12:03 Rene Ladan (rene) search for other commits by this committer
cleanup: Remove expired ports:

2022-03-11 databases/postgresql96-client: PostgreSQL-9.6 has reached end-of-life
2022-03-11 databases/postgresql96-contrib: PostgreSQL-9.6 has reached
end-of-life
2022-03-11 databases/postgresql96-docs: PostgreSQL-9.6 has reached end-of-life
databases/postgresql96-pgtcl: part of expired PostgreSQL 9.6
2022-03-11 databases/postgresql96-plperl: PostgreSQL-9.6 has reached end-of-life
2022-03-11 databases/postgresql96-plpython: PostgreSQL-9.6 has reached
end-of-life
2022-03-11 databases/postgresql96-pltcl: PostgreSQL-9.6 has reached end-of-life
2022-03-11 databases/postgresql96-server: PostgreSQL-9.6 has reached end-of-life
commit hash: 7b10329e431b4bc020d0c00abe9c0022be6fe6a8 commit hash: 7b10329e431b4bc020d0c00abe9c0022be6fe6a8 commit hash: 7b10329e431b4bc020d0c00abe9c0022be6fe6a8 commit hash: 7b10329e431b4bc020d0c00abe9c0022be6fe6a8 7b10329
Thursday, 11 Nov 2021
14:37 Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-*: updated to latest version

This release contains a variety of fixes from the previous version.

A dump/restore is not required for those running the same major version.
However, note that installations using physical replication should
update standby servers before the primary server, as explained in the
release notes.

Also, several bugs have been found that may have resulted in corrupted
indexes, as explained in the next several changelog entries.  If any of
those cases apply to you, it's recommended to reindex possibly-affected
indexes after updating.

This release also mitigates two possible man-in-the-middle attacks.

Security:	2ccd71bd-426b-11ec-87db-6cc21735f730
Release notes:	https://www.postgresql.org/docs/release/14.1/
commit hash: d3db7630c79762949ca7d0f3cbf1db128ebecca4 commit hash: d3db7630c79762949ca7d0f3cbf1db128ebecca4 commit hash: d3db7630c79762949ca7d0f3cbf1db128ebecca4 commit hash: d3db7630c79762949ca7d0f3cbf1db128ebecca4 d3db763
Sunday, 17 May 2020
20:37 girgen search for other commits by this committer
The PostgreSQL Global Development Group has released an update to all
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], Loic Bartoletti [2]
Original commitRevision:535676 
Friday, 15 Feb 2019
11:02 girgen search for other commits by this committer
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
`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]
Original commitRevision:492989 
Friday, 10 Aug 2018
09:25 girgen search for other commits by this committer
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
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
Original commitRevision:476819 
Thursday, 8 Feb 2018
17:38 girgen search for other commits by this committer
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.

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
Original commitRevision:461251 
Thursday, 9 Nov 2017
16:11 girgen search for other commits by this committer
Update to latest versions of PostgreSQL

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/
Original commitRevision:453847 
Monday, 17 Jul 2017
11:14 amdmi3 search for other commits by this committer
- Add missing file to plist

PR:		217874
Approved by:	maintainer timeout (postgres, 2 weeks)
Original commitRevision:446064 
Thursday, 11 May 2017
14:28 girgen search for other commits by this committer
PostgreSQL security updates

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.
Original commitRevision:440628 
Thursday, 9 Feb 2017
15:22 girgen search for other commits by this committer
PostgreSQL 9.6.2, 9.5.6, 9.4.11, 9.3.16 and 9.2.20 released!

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/
Original commitRevision:433738 
Thursday, 27 Oct 2016
14:04 girgen search for other commits by this committer
Update PostgreSQL to latest versions.

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.
Original commitRevision:424765 
Thursday, 29 Sep 2016
13:37 girgen search for other commits by this committer
PostgreSQL 9.6, the latest version of the world's leading open source
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.
Original commitRevision:422916 
Monday, 5 Sep 2016
11:59 girgen search for other commits by this committer
Fix broken package name for PostgreSQL 9.6 RC1
Fix bad pkg-plist for postgresql 9.6 server
Original commitRevision:421361 
11:15 girgen search for other commits by this committer
Add PostgreSQL-9.6 RC1

Please read the entry from 20160905 in UPDATING:

daemon user has changed to `postgres'
ICU is default on
Original commitRevision:421360 

Number of commits found: 14