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
non port: databases/postgresql96-server/Makefile

Number of commits found: 52

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
Friday, 11 Feb 2022
13:00 Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql96-*: mark ports as expired

Final release was November 11, 2021.

URL:	https://www.postgresql.org/support/versioning/
commit hash: 22be58e52f34646e98b8c4e1fcbb304b790ccf9b commit hash: 22be58e52f34646e98b8c4e1fcbb304b790ccf9b commit hash: 22be58e52f34646e98b8c4e1fcbb304b790ccf9b commit hash: 22be58e52f34646e98b8c4e1fcbb304b790ccf9b 22be58e
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
Thursday, 28 Oct 2021
16:37 Jan Beich (jbeich) search for other commits by this committer
devel/icu: update to 70.1

Changes:	https://github.com/unicode-org/icu/releases/tag/release-70-1
Reported by:	GitHub (watch releases)
PR:		258794
Exp-run by:	antoine
commit hash: f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3 commit hash: f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3 commit hash: f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3 commit hash: f34ece3aa6a292628ea75c0e4dd2a04d879ab0a3 f34ece3
Thursday, 12 Aug 2021
16:23 Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql*: update to latest versions

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
commit hash: a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5a commit hash: a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5a commit hash: a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5a commit hash: a271b9d5b7b2c0eb57d1a09fc44f2ecbbad7bc5a a271b9d
Tuesday, 1 Jun 2021
13:59 Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-server: rc-script should require DAEMON

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
commit hash: 8d831eb43aba59013b948830cbd4b22b45deb223 commit hash: 8d831eb43aba59013b948830cbd4b22b45deb223 commit hash: 8d831eb43aba59013b948830cbd4b22b45deb223 commit hash: 8d831eb43aba59013b948830cbd4b22b45deb223 8d831eb
Thursday, 20 May 2021
14:38 Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql14-*: Add postgresql 14 beta1 the the ports tree.

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.
commit hash: fccc45e5ff4a8aea150005196c0d4f2cbaeed5db commit hash: fccc45e5ff4a8aea150005196c0d4f2cbaeed5db commit hash: fccc45e5ff4a8aea150005196c0d4f2cbaeed5db commit hash: fccc45e5ff4a8aea150005196c0d4f2cbaeed5db fccc45e
Saturday, 15 May 2021
09:12 Palle Girgensohn (girgen) search for other commits by this committer
databases/postgresql??-*: Upgrade to latest version

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/
commit hash: ab83f2b4bb78a718efa5c43247ba1e1d207f99b6 commit hash: ab83f2b4bb78a718efa5c43247ba1e1d207f99b6 commit hash: ab83f2b4bb78a718efa5c43247ba1e1d207f99b6 commit hash: ab83f2b4bb78a718efa5c43247ba1e1d207f99b6 ab83f2b
Thursday, 8 Apr 2021
23:33 Jan Beich (jbeich) search for other commits by this committer
devel/icu: update to 69.1

Changes:	https://github.com/unicode-org/icu/releases/tag/release-69-1
Reported by:	GitHub (watch releases)
commit hash: 69d24a727d44d398f7357cb844386f3ec4750a4f commit hash: 69d24a727d44d398f7357cb844386f3ec4750a4f commit hash: 69d24a727d44d398f7357cb844386f3ec4750a4f commit hash: 69d24a727d44d398f7357cb844386f3ec4750a4f 69d24a7
Tuesday, 6 Apr 2021
14:31 Mathieu Arnold (mat) search for other commits by this committer
Remove # $FreeBSD$ from Makefiles.
commit hash: 305f148f482daf30dcf728039d03d019f88344eb commit hash: 305f148f482daf30dcf728039d03d019f88344eb commit hash: 305f148f482daf30dcf728039d03d019f88344eb commit hash: 305f148f482daf30dcf728039d03d019f88344eb 305f148
Thursday, 11 Feb 2021
14:34 girgen search for other commits by this committer
PostgreSQL 13.2, 12.6, 11.11, 10.16, 9.6.21, and 9.5.25 released

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
Original commitRevision:564956 
Thursday, 12 Nov 2020
15:00 girgen search for other commits by this committer
PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20 released!

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
Original commitRevision:554966 
Tuesday, 3 Nov 2020
00:56 jbeich search for other commits by this committer
devel/icu: update to 68.1

Changes:	http://site.icu-project.org/download/68
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
Reported by:	GitHub (watch releases)
Original commitRevision:553940 
Thursday, 24 Sep 2020
13:33 girgen search for other commits by this committer
Welcome PostgreSQL 13

Release notes:	https://www.postgresql.org/about/news/2077/
Original commitRevision:549921 
Thursday, 13 Aug 2020
13:45 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.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
Original commitRevision:544810 
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 
Thursday, 23 Apr 2020
20:14 jbeich search for other commits by this committer
devel/icu: update to 67.1

Changes:	http://site.icu-project.org/download/67
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
Reported by:	GitHub (watch releases)
Original commitRevision:532707 
Friday, 13 Mar 2020
09:54 jbeich search for other commits by this committer
Fix up PORTREVISION style after "portedit bump-revision"
Original commitRevision:528344 
09:47 jbeich search for other commits by this committer
devel/icu: update to 66.1

Changes:	http://site.icu-project.org/download/66
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
Original commitRevision:528343 
Thursday, 13 Feb 2020
19:14 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.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
Original commitRevision:526063 
Thursday, 14 Nov 2019
16:24 girgen search for other commits by this committer
Upgrade PostgreSQL

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/
Original commitRevision:517600 
Thursday, 3 Oct 2019
20:35 jbeich search for other commits by this committer
devel/icu: update to 65.1

Changes:	http://site.icu-project.org/download/65
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
Original commitRevision:513733 
Thursday, 8 Aug 2019
15:33 girgen search for other commits by this committer
iThe PostgreSQL Global Development Group has released an update to all
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.
Original commitRevision:508390 
Friday, 26 Jul 2019
20:46 gerald search for other commits by this committer
Bump PORTREVISION for ports depending on the canonical version of GCC
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
Original commitRevision:507372 
Thursday, 27 Jun 2019
21:28 girgen search for other commits by this committer
Upgrade PostgreSQL to latest version

The PostgreSQL Global Development Group has released an update to all supported
versions of our database system, including 11.4, 10.9, 9.6.14, 9.5.18, and
9.4.23, as well as the second beta of PostgreSQL 12. This release fixes one
security issue and over 25 bugs since the previous cumulative update in May.

This release is made outside of the normal update release schedule as the
security vulnerability was determined to be critical enough to distribute the
fix as quickly as possible. Users who are running PostgreSQL 10, PostgreSQL 11,
or the PostgreSQL 12 beta should upgrade as soon as possible.

All other users should plan to apply this update at the next scheduled
downtime.

Release notes:	https://www.postgresql.org/about/news/1949/
Security:	245629d4-991e-11e9-82aa-6cc21735f730
Original commitRevision:505245 
Thursday, 9 May 2019
22:32 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.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]
Original commitRevision:501149 
Thursday, 25 Apr 2019
18:34 crees search for other commits by this committer
Don't overwrite PORTREVISION from the slave, following readline update.

I've had to bump revision for several slaves here, but most will not
be rebuilt, except the -client slaves.  Apologies for anyone having
to rebuild -clients unnecessarily, but it's not a heavy task- better safe
than sorry.

PR:		ports/236156
Reported by:	Andrew Dunstan (PostgreSQL), koobs, Dmitri Goutnik
Original commitRevision:500060 
Wednesday, 27 Mar 2019
21:11 jbeich search for other commits by this committer
devel/icu: update to 64.1

Changes:	http://site.icu-project.org/download/64
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		236325
Exp-run by:	antoine
Differential Revision:	https://reviews.freebsd.org/D19479
Original commitRevision:496981 
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 
Wednesday, 12 Dec 2018
01:35 gerald search for other commits by this committer
Bump PORTREVISION for ports depending on the canonical version of GCC
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
Original commitRevision:487272 
Thursday, 8 Nov 2018
23:21 girgen search for other commits by this committer
Posted on 2018-11-08 by PostgreSQL Global Development Group The PostgreSQL
Global Development Group has released an update to all supported versions of
our database system, including 11.1, 10.6, 9.6.11, 9.5.15, 9.4.20, and 9.3.25.
This release fixes one security issue as well as bugs reported over the last
three months.

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 if you are using pg_stat_statements in your installation.

This update is also the final release for PostgreSQL 9.3, which is now
end-of-life and will no longer receive any bug or security fixes. If your
environment still uses PostgreSQL 9.3, please make plans to update to a
community supported version as soon as possible. Please see our versioning
policy for more information.

Releasenotes:	https://www.postgresql.org/about/news/1905/
Security:	1c27a706-e3aa-11e8-b77a-6cc21735f730
Security:	CVE-2018-16850
Original commitRevision:484488 
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 
Friday, 29 Jun 2018
14:22 jbeich search for other commits by this committer
devel/icu: update to 62.1

Changes:	http://site.icu-project.org/download/62
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		229359
Exp-run by:	antoine (only 10.4)
Original commitRevision:473551 
Friday, 11 May 2018
13:10 girgen search for other commits by this committer
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.
Original commitRevision:469638 
Friday, 6 Apr 2018
15:53 jbeich search for other commits by this committer
devel/icu: update to 61.1

Changes:	http://site.icu-project.org/download/61
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		227042
Exp-run by:	antoine
MFH:		2018Q2 (required by Firefox 61)
Original commitRevision:466648 
Thursday, 1 Mar 2018
15:10 girgen search for other commits by this committer
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
Original commitRevision:463327 
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 
02:31 jbeich search for other commits by this committer
devel/icu: update to 60.1

Changes:	http://site.icu-project.org/download/60
ABI:		https://abi-laboratory.pro/tracker/timeline/icu4c/
PR:		223373
Exp-run by:	antoine
Original commitRevision:453790 
Monday, 25 Sep 2017
00:02 jbeich search for other commits by this committer
devel/icu: update to 59.1

- Temporarily keep C++98 working in consumers for Clang's default -std=

Changes:	http://site.icu-project.org/download/59
PR:		218788
Submitted by:	takefu@airport.fm, dcarmich@dcarmichael.net (early version)
Exp-run by:	antoine
Original commitRevision:450556 
Tuesday, 5 Sep 2017
09:27 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 9.6.5, 9.5.9,
9.4.14, 9.3.19, and 9.2.23.

This release includes fixes that prevent a crash in pg_restore when
using parallel mode. It also patches over a few other bugs reported
since the last releases in August.

Additionally, in 9.4.14 only, there is a fix to an issue with walsenders
preventing primary-server shutdown unless immediate shutdown mode is used.

Users should plan to update at the next convenient downtime.

Bug Fixes and Improvements

This update also fixes a number of bugs reported in the last few weeks.
Some of these issues affect only version 9.6, but many affect all
supported versions:

* Show foreign tables in information_schema.table_privileges view.
This fix applies to new databases, see the release notes for the
procedure to apply the fix to an existing database.
* Correctly identify columns that are of a range type or domain type
over a composite type or domain type being searched for
* Prevent crash when passing fixed-length pass-by-reference data types
to parallel worker processes
* Change ecpg's parser to allow RETURNING clauses without attached C
variables
* Change ecpg's parser to recognize backslash continuation of C
preprocessor command lines
* Improve selection of compiler flags for PL/Perl on Windows
Original commitRevision:449278 
Thursday, 10 Aug 2017
14:21 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 9.6.4, 9.5.8,
9.4.13, 9.3.18, and 9.2.22. This release fixes three security issues.
It also patches over 50 other bugs reported over the last three months.
Users who are affected by the below security issues should update as
soon as possible.  Users affected by CVE-2017-7547
(https://access.redhat.com/security/cve/CVE-2017-7547) will need to
perform additional steps after upgrading to resolve the issue.  Other
users should plan to update at the next convenient downtime.

URL:		https://www.postgresql.org/about/news/1772/
Security:	CVE-2017-7546, CVE-2017-7547, CVE-2017-7548
Original commitRevision:447678 
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 
Saturday, 24 Sep 2016
11:06 tijl search for other commits by this committer
- Update devel/icu to 57.1.
- Clean up the Makefile.
- Follow some upstream recommendations (--with-data-packaging=archive,
  --disable-renaming, -DICU_NO_USER_DATA_OVERRIDE).
- Patch makefiles to install static libraries with INSTALL_DATA so they
  aren't stripped.
- Patch config/mh-bsd-gcc to sync with config/mh-linux-gcc.
- Fix endianness detection in ICU.  The code wanted to use BYTE_ORDER
  defined in machine/endian.h, but this isn't visible because ICU is
  compiled with _XOPEN_SOURCE.  Patch the code to use _BYTE_ORDER instead.
- Compile ICU with C++11 compiler to enable move constructors.
- Patch ICU to fix a problem with atomics in the case of a C++11 compiler
  without C++11 header <atomic> (like Clang on FreeBSD 9).
- Bump all ports that depend on it due to library version change.
- Add USES=compiler:c++0x to some ports that pick up -std=c++0x from ICU
  pkgconfig files.
- Add USES=compiler:c++11-lib to graphics/libcdr01 because it also needs
  a C++11 runtime library now.  Add this to all ports that depend on it
  so their executables load the right libstdc++.so on FreeBSD 9.

PR:		205120
Exp-run by:	antoine
Approved by:	portmgr (antoine)
Original commitRevision:422711 
Wednesday, 21 Sep 2016
09:02 girgen search for other commits by this committer
We should tell initdb which user we want as DBA
Original commitRevision:422551 
Wednesday, 7 Sep 2016
01:57 girgen search for other commits by this committer
Fix plist problem for postgresql-9.6 [1]

Fix spelling while here [2]

Pointed out by:	matthew [1], bcr [2]
Pointy hat to:	girgen
Original commitRevision:421475 
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: 52