Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
This is a slave port. You may also want to view the commits to the master port: databases/pgtcl |
Commit | Credits | Log message |
2.1.1_2 11 Mar 2022 12:03:56 |
Rene Ladan (rene) |
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 |
2.1.1_2 29 Oct 2021 09:50:18 |
Stefan Eßer (se) |
*/*: Remove redundant '-[0-9]*' from CONFLICTS
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".
Approved by: portmgr (blanket) |
2.1.1_2 07 Apr 2021 08:09:01 |
Mathieu Arnold (mat) |
One more small cleanup, forgotten yesterday.
Reported by: lwhsu |
2.1.1_2 06 Apr 2021 14:31:07 |
Mathieu Arnold (mat) |
Remove # $FreeBSD$ from Makefiles. |
2.1.1_2 08 Aug 2019 15:33:03 |
girgen |
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. (Only the first 15 lines of the commit message are shown above ) |
2.1.1_2 26 Jul 2019 20:46:57 |
gerald |
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 |
2.1.1_1 27 Jun 2019 21:28:00 |
girgen |
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 |
2.1.1_1 25 Apr 2019 18:34:42 |
crees |
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 |
2.1.1_1 15 Feb 2019 11:02:22 |
girgen |
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 ) |
2.1.1_1 12 Dec 2018 01:35:36 |
gerald |
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 |
2.0.0_1 05 Sep 2016 11:15:29 |
girgen |
Add PostgreSQL-9.6 RC1
Please read the entry from 20160905 in UPDATING:
daemon user has changed to `postgres'
ICU is default on |