| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 14.2, 13.6, 12.10, 11.15,
and 10.20. This release fixes over 55 bugs reported over the last three
months.
Announcement: https://www.postgresql.org/about/news/postgresql-142-136-1210-1115-and-1020-released-2402/
Release notes: https://www.postgresql.org/docs/release/
|
| |
|
|
| |
Remove stale patch since it redefines the code that is already upstream.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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/
|
| |
|
|
|
|
|
| |
Changes: https://github.com/unicode-org/icu/releases/tag/release-70-1
Reported by: GitHub (watch releases)
PR: 258794
Exp-run by: antoine
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
postgresql??-contrib fails to build for versions below 13 when building
in parallel. Needs more investigation.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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/
|
| | |
|
| |
|
|
|
| |
Reported by: tmunro
Reviewed by: girgen
|
| |
|
|
|
| |
Changes: https://github.com/unicode-org/icu/releases/tag/release-69-1
Reported by: GitHub (watch releases)
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The obscure message being:
sed: 4: /tmp/sed_plist_sub.1i0ZNBB8: RE error: trailing backslash (\)
Thanks to: kevans
|
| |
|
|
|
|
| |
(ignoring case)
Reported by: danfe (for net/mosquitto), portscan
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
PR: 251192 (Submitted by Dmitry Marakasov)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Changes: http://site.icu-project.org/download/68
ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/
Reported by: GitHub (watch releases)
|
| |
|
|
|
|
|
| |
Make LLVM option work again on everything but powerpc64.
PR: 250346
Submitted by: Christian Ullrich
|
| |
|
|
|
| |
PR: 250241
Submitted by: O. Hartmann
|
| |
|
|
|
|
| |
This will still keep this port and its slaves buildable on the package builder on powerpc64, and I doubt anyone uses it on mips*.
Reported by: kib@, adamw@
|
| |
|
|
|
|
| |
Move LLVM option configuration after including bsd.port.options.mk.
Reported by: kib@
|
| |
|
|
| |
Add the previously removed disabling of LLVM when it's not in base.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
ports version. Fix this by depending on a higher version of llvm if such a
version exixts, and otherwise use a clang version compatible with the latest
llvm.
Using llvm was previously dependant on clang being used, and this did not quite
work for all cases due to some weird order of variables in the Makefile. The
result was that the option set by the used was not really honored. The
portrevision is bumped to reflect that the setting of LLVM might not have
worked before this portrevison.
PR: 244403
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix a plist issue [1].
Make sure the LLVM options are correctly handled. Setting the OPTIONS_DEFAULT
conditionally based on wheather the default compiler is cland doesn't work
properly, it is always set even if you deselect it. Just setting it per default
seems to work better.
Attempt a fix for building on FreeBSD-13.0 where clang is newer than the
default LLVM. First attempt is to use an lower version clang to match what LLVM
has as default. [2]
PR: 244403 [2], 249933 [2], 249875 [1]
|
| |
|
|
| |
Submitted by: Raivo Hool
|
|
|
Release notes: https://www.postgresql.org/about/news/2077/
|