| non port: databases/postgresql10-server/Makefile |
Number of commits found: 64 | |
Tuesday, 7 Mar 2023
|
21:40 Rene Ladan (rene) 
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
    3839b19 | |
Tuesday, 7 Feb 2023
|
17:34 Palle Girgensohn (girgen)
databases/postgresql10-*: PostgreSQL-10 has reached end-of-life
264342c | |
Tuesday, 15 Nov 2022
|
15:40 Dmitry Marakasov (amdmi3)
databases/postgresql*-server: require mountlate in rc.d scripts
PostgreSQL server may use late-mounted filesystems, so require these
in rc.d scripts. Real life example is when /tmp is late-mounted tmpfs
atop of ZFS, and if posgresql-server starts before mountlate, its
socket which resides on /tmp is hidden under tmpfs which is mounted
afterwards.
PR: 267500
Approved by: maintainer timeout (pgsql, 2 weeks)
d512e8c | |
Thursday, 10 Nov 2022
|
16:23 Palle Girgensohn (girgen)
databases/postgresq??-*: update to latest version
PostgreSQL 15.1, 14.6, 13.9, 12.13, 11.18, and 10.23 Released!
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 15.1, 14.6, 13.9, 12.13,
11.18, and 10.23. This release fixes 25 bugs reported over the last
several months.
This is the final release of PostgreSQL 10. PostgreSQL 10 will no longer
receive security and bug fixes. If you are running PostgreSQL 10 in a
production environment, we suggest that you make plans to upgrade.
Release notes: https://www.postgresql.org/docs/release/
792a1db | |
Wednesday, 19 Oct 2022
|
08:10 Jan Beich (jbeich)
devel/icu: update to 72.1
Changes: https://github.com/unicode-org/icu/releases/tag/release-72-1
Reported by: GitHub (watch releases)
PR: 266582
Exp-run by: antoine
dfe25d7 | |
Monday, 3 Oct 2022
|
10:53 Palle Girgensohn (girgen)
databases/postgresql1[012]-server: fix bad plist (again)
Previous fix was incomplete and plain wrong. Fix properly.
Noted by: sunpoet@
72588c5 | |
Saturday, 10 Sep 2022
|
17:41 Stefan Eßer (se) Author: Tobias Kortkamp
Fix WWW in parent/child ports
Many of the WWW are overwritten later which means the wrong value
is used. This did not happen before where the children were either
a) just using the pkg-descr from the parents
b) or had their own separate pkg-descr with custom WWW
Use WWW?= in parents when the child's WWW is different.
Children that use the same WWW as the parent can just inherit it,
i.e., the child WWW can be removed.
Approved by: portmgr (implicit)
e79fe1a | |
Wednesday, 7 Sep 2022
|
21:10 Stefan Eßer (se)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)
b7f0544 | |
Friday, 12 Aug 2022
|
09:05 Palle Girgensohn (girgen)
databases/postgresql??-*: Update to latest version
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 14.5, 13.8, 12.12, 11.17,
and 10.22, as well as the third beta release of PostgreSQL 15. This
release closes one security vulnerability and fixes over 40 bugs
reported over the last three months.
PostgreSQL 10 will stop receiving fixes on November 10, 2022. If you are
running PostgreSQL 10 in a production environment, we strongly advise
that you make plans to upgrade to a newer, supported version of
PostgreSQL so you can continue to receive bug and security fixes.
Security: CVE-2022-2625
Release
notes: https://www.postgresql.org/about/news/postgresql-145-138-1212-1117-1022-and-15-beta-3-released-2496/
2e7e556 | |
Wednesday, 20 Jul 2022
|
14:21 Tobias C. Berner (tcberner)
databases: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* "Choe, Cheng-Dae" whitekid
* "Mahdi Mokhtari <mokhi64@gmail.com>"
* "Meikel Brandmeyer" <ocaml-sqlite3-port@kotka.de>
* <hvo.pm@xs4all.nl>
* <jsmith@resonatingmedia.com>
* <ports@c0decafe.net>
* Aaron Dalton <aaron@FreeBSD.org>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
* Akinori MUSHA aka knu <knu@idaemons.org>
* Alan Snelson <Alan@Wave2.org>
* Aldis Berjoza <graudeejs@gmail.com>
* Alessando Sagratini <ale_sagra@hotmail.com>
* Alex Dupre <ale@FreeBSD.org>
* Alex Samorukov <samm@freebsd.org>
* Alexander Logvinov <ports@logvinov,com>
* Alexander Logvinov <ports@logvinov.com>
* Alexander Nedotsukov <bland@FreeBSD.org>
* Alexander Novitsky
* Alexander Zhuravlev <zaa@zaa.pp.ru>
* Alexey Degtyarev <alexey@renatasystems.org>
* Alexey Dokuchaev <danfe@FreeBSD.org>
* Anders Nordby <anders@fix.no>
* Andrei Antoukh <niwi@niwi.be>
* Andrew McNaughton <andrew@scoop.co.nz>
* Andrew Pantyukhin <infofarmer@FreeBSD.org>
* Andrey Kostenko <andrey@kostenko.name>
* Andrey Simonenko
* Andrey Zakhvatov
* Anes Mukhametov <anes@anes.su>
* Anton Berezin <tobez@FreeBSD.org>
* Anton Berezin <tobez@tobez.org>
* Antonio Carlos Venancio Junior (<antonio@inf.ufsc.br>)
* Antonio Carlos Venancio Junior (<antonio@php.net>)
* Autrijus Tang <autrijus@autrijus.org>
* Babak Farrokhi <farrokhi@FreeBSD.org>
* Bartek Rutkowski <r@robakdesign.com>
* Bernard Spil <brnrd@FreeBSD.org>
* Brent J. Nordquist <bjn@visi.com>
* Cezary Morga <cm@therek.net>
* Cheng-Lung Sung <clsung@FreeBSD.org>
* Choe, Cheng-Dae
* Chris D. Faulhaber <jedgar@FreeBSD.org>
* Chris Larsen <darth@vader.dk>
* Damian Gerow <dgerow@afflictions.org>
* Daniel O'Connor
* Daniel Wijnands <daniel@itxl.nl>
* Dave Green <dg@fastmail.co.uk>
* David Thiel <lx@FreeBSD.org>
* Davíð Steinn Geirsson <david@isnic.is>
* Denis Generalov <gd.workbox@gmail.com>
* Denis Generalov <gd@rambler-co.ru>
* Denis Shaposhnikov <dsh@bamus.cz>
* Dermot Tynan <dtynan@kalopa.com>
* Dmitry Liakh <dliakh@ukr.net>
* Dmitry Sivachenko <demon@FreeBSD.org>
* Dmitry Sivachenko <dima@Chg.RU>
* Dmitry Sivachenko <mitya@yandex-team.ru>
* Domas Mituzas <midom@dammit.lt>
* Dominic Mitchell
* Don Owens <don@regexguy.com>
* Dryice Dong Liu <dryice@dryice.name>
* Edwin Groothuis (edwin@mavetju.org)
* Eric Freeman <freebsdports@chillibear.com>
* Espen Tagestad <espen@tagestad.no>
* Espen Volden aka voldern <voldern@hoeggen.net>
* Evan Sarmiento <bsdports@wayfair.com>
* Fernan Aguero <fernan@iib.unsam.edu.ar>
* Frank Wall <fw@moov.de>
* Ganbold Tsagaankhuu <ganbold@FreeBSD.org>
* Gary Palmer <gpalmer@FreeBSD.org>
* Gea-Suan Lin <gslin@gslin.org>
* Geraud CONTINSOUZAS <geraud@gcu.info>
* Gerrit Beine <tux@pinguru.net>
* Greg Larkin <glarkin@FreeBSD.org>
* Grzegorz Blach <gblach@FreeBSD.org>
* Hansjoerg Pehofer <hansjoerg.pehofer@uibk.ac.at>
* Henk van Oers <hvo.pm@xs4all.nl>
* Henrik Hodne <henrik@hodne.io>
* Hiroyuki Hanai <hanai@FreeBSD.org>
* Horia Racoviceanu <horia@racoviceanu.com>
* Hye-Shik Chang
* Hye-Shik Chang <perky@python.or.kr>
* Ilia Chipitsine <ilia@jane.cgu.chel.su>
* Ivan Voras <ivoras@FreeBSD.org>
* J.F. Dockes
* Jaap Boender <jaapb@kerguelen.org>
* Jake Smith <jake@xz.cx>
* James FitzGibbon <jfitz@FreeBSD.org>
* Janos Mohacsi <janos.mohacsi@bsd.hu>
* Janos.Mohacsi@bsd.hu
* Jason Helfman <jgh@FreeBSD.org>
* Jens Rehsack <rehsack@liwing.de>
* Jeremy Chadwick <koitsu@FreeBSD.org>
* Jev Björsell <ports@ecadlabs.com>
* Jim Ohlstein <jim@ohlste.in>
* Jin-Shan Tseng <tjs@cdpa.nsysu.edu.tw>
* Joe Horn <joehorn@gmail.com>
* Joe Marcus Clarke <marcus@FreeBSD.org>
* Johannes Meixner <johannes@perceivon.net>
* John Chen <johnpupu@gmail.com>
* John Marino <marino@FreeBSD.org>
* John Merryweather Cooper
* John Merryweather Cooper et al
* Jon Nistor <nistor@snickers.org>
* Jonathan Weiss (<jw@innerewut.de>)
* Jose Jachuf <jjachuf@gmail.com>
* Joshua D. Abraham <jabra@ccs.neu.edu>
* Jov <amutu@amutu.com>
* Jov amutu@amutu.com
* Jui-Nan Lin <jnlin@freebsd.cs.nctu.edu.tw>
* Julien Laffaye <kimelto@gmail.com>
* Jyun-Yan You <jyyou@cs.nctu.edu.tw>
* Keith Gaughan <k@sterechro.me>
* Kevin Bowling <kbowling@freebsd.org>
* Kimo <kimor79@yahoo.com>
* Kimura Fuyuki <fuyuki@nigredo.org>
* Koop Mast <kwm@FreeBSD.org>
* Lars Balker Rasmussen <lbr@FreeBSD.org
* Lars Balker Rasmussen <lbr@FreeBSD.org>
* Lars Eggert <larse@isi.edu>
* Lars Thegler <lars@thegler.dk>
* Lars Thegler <lth@FreeBSD.org>
* Li-Wen Hsu <lwhsu@FreeBSD.org>
* Loïc BARTOLETTI
* Loïc BARTOLETTI <lbartoletti@FreeBSD.org>
* Lubomir Marinov <lubomir_m@abv.bg>
* Mahdi Mokhtari <mokhi64@gmail.com>
* Mahlon E. Smith <mahlon@martini.nu>
* Marc G. Fournier <scrappy@FreeBSD.org>
* Mark Felder <feld@FreeBSD.org>
* Markus Brueffer <markus@FreeBSD.org>
* Martin Matuska <martin@matuska.org>
* Martin Matuska <mm@FreeBSD.org>
* Martin Wilke <miwi@FreeBSD.org>
* Mathieu Arnold <m@absolight.net>
* Matthew Seaman
* Matthias Andree <mandree@FreeBSD.org>
* Matthias Fechner <mfechner@FreeBSD.org>
* Matthias Petermann <matthias@petermann-it.de>
* Max Khon
* Max Khon <fjoe@FreeBSD.org>
* Michael Johnson <ahze@FreeBSD.org>
* Michael Johnson <ahze@ahze.net>
* Michael Winking <mwfp@foldl.net>
* Mikael URANKAR and Loïc BARTOLETTI
* Mike Carlson (carlson39@llnl.gov)
* Mikhail T. <michael@fun-box.ru>
* Mikhail Teterin
* Mikhail Teterin <mi@aldan.algebra.com>
* Mikolaj Golub <trociny@FreeBSD.org>
* Mirko Zinn <mail@derzinn.de>
* Mohammad S. Babaei <info@babaei.net>
* Muhammad Moinur Rahman <bofh@FreeBSD.org>
* Nick Hibma <n_hibma@freebsd.org>
* Nick Hilliard <nick@foobar.org>
* Nick Sayer <nsayer@FreeBSD.org>
* Nicola Vitale <nivit@FreeBSD.org>
* Nicolas Embriz <nbari@tequila.io>
* Nicolas de Bari Embriz <nbari@dalmp.com>
* Oleg Sharoiko <os@rsu.ru>
* Olexander Melnyk <olexander.v.melnyk@gmail.com>
* Oliver Eikemeier <eikemeier@fillmore-labs.com>
* Olivier Duchateau <duchateau.olivier@gmail.com>
* Palle Girgensohn <girgen@FreeBSD.org>
* Palle Girgensohn <girgen@partitur.se>
* Palle Girgensohn <girgen@pingpong.net>
* Parv <parv@pair.org>
* Pete Fritchman <petef@databits.net>
* Peter Avalos <pavalos@theshell.com>
* Philip M. Gollucci
* Philip M. Gollucci <philip@p6m7g8.com>
* Philip Stoev <philip.stoev@galeracluster.com>
* Pierre-Emmanuel Andre <pea@raveland.org>
* Pietro Cerutti <gahr@FreeBSD.org>
* Piotr Kubaj <pkubaj@anongoth.pl>
* Po-Chuan Hsieh <sunpoet@FreeBSD.org>
* Qing Feng <qingfeng@douban.com>
* Quinton Dolan <q@onthenet.com.au>
* Radim Kolar
* Rainer Hurling <rhurlin@gwdg.de>
* Rick Miller
* Robert Kruus <rob.kruus@gmail.com>
* Rod Taylor <ports@rbt.ca>
* Roland van Laar <roland@micite.net>
* Rong-En Fan <rafan@FreeBSD.org>
* Roy Boerner
* Rozhuk Ivan <rozhuk.im@gmail.com>
* Rusty Nejdl
* Ryan Steinmetz <rpsfa@rit.edu>
* Ryan Steinmetz <zi@FreeBSD.org>
* Ryan T. Dean <rtdean@cytherianage.net>
* Sam Lawrance <boris@brooknet.com.au>
* Scott McWhirter <scott@surreytech.co.uk>
* Seamus Venasse <svenasse@polaris.ca>
* Sean Chittenden <seanc@FreeBSD.org>
* Sergei Kolobov <sergei@kolobov.com>
* Sergei Vyshenski <svysh.fbsd@gmail.com>
* Sergey A. Osokin <osa@FreeBSD.org.ru>
* Sergey A. Osokin <osa@FreeBSD.org>
* Sergey Matveychuk <sem@FreeBSD.org>
* Sergey Skvortsov <skv@FreeBSD.org>
* Sergey Skvortsov <skv@protey.ru>
* Sevan Janiyan <venture37@geeklan.co.uk>
* Sheldon Hearn <sheldonh@FreeBSD.org>
* Stanislav Svirid <count@211.ru>
* Stefan Schmidt <stefan.schmidt@stadtbuch.de>
* Steve Wills <swills@FreeBSD.org>
* Steve Wills <swills@freebsd.org>
* Steven Kreuzer <skreuzer@FreeBSD.org>
* Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>
* Sunpoet Po-Chuan Hsieh <sunpoet@sunpoet.net>
* T. William Wells <bill@twwells.com>
* TAKATSU Tomonari <tota@FreeBSD.org>
* Thierry Thomas (<thierry@pompo.net>)
* Thomas Gellekum <tg@FreeBSD.org>
* Timur I. Bakeyev <bat@cpan.org>
* Tom Judge <tj@FreeBSD.org>
* Torsten Zuehlsdorff <ports@toco-domains.de>
* Torsten Zuhlsdorff <ports@toco-domains.de>
* Toshiya Saitoh (<toshiya@saitoh.nu>)
* Tsung-Han Yeh <snowfly@yuntech.edu.tw>
* Vasil Dimov <vd@FreeBSD.org>
* Veniamin Gvozdikov <vg@FreeBSD.org>
* Vladimir Timofeev <vovkasm@gmail.com>
* Wen Heping
* Wen Heping <wen@FreeBSD.org>
* Wen Heping <wenheping@gmail.com>
* Wen heping <wenheping@gmail.com>
* William Grzybowski <wg@FreeBSD.org>
* Xin Li <delphij@FreeBSD.org>
* Yarema <yds@CoolRat.org>
* Yarema <yds@Necessitu.de>
* Yen-Ming Lee <leeym@FreeBSD.org>
* Ying-Chieh Liao <ijliao@FreeBSD.org>
* Yoichi NAKAYAMA <yoichi@FreeBSD.org>
* Yuri Victorovich <yuri@rawbw.com>
* Zach Thompson <hideo@lastamericanempire.com>
* Zach Thompson <lin-chi@lastamericanempire.com>
* ache@FreeBSD.org
* alfred
* alp@sfedu.ru
* andrew@scoop.co.nz
* andrey@kostenko.name
* chinsan
* chinsan <chinsan.tw@gmail.com>
* clive
* clive@FreeBSD.org
* clsung@dragon2.net
* dcf@aracnet.com
* elvstone@gmail.com
* erikhb@bgnett.no
* erwin@FreeBSD.org
* gahr
* ijliao
* ijlioa
* ivoras
* johnpupu <johnpupu@gmail.com>
* kirk@daycos.com
* kuriyama
* lbartoletti <lbartoletti@FreeBSD.org>
* loïc bartoletti <lbartoletti@FreeBSD.org>
* mharo@FreeBSD.org
* michael johnson <ahze@ahze.net>
* milki <milki@rescomp.berkeley.edy>
* mm@FreeBSD.org
* nbm
* nectar@FreeBSD.org
* nork@FreeBSD.org
* nork@cityfujisawa.ne.jp
* olevole@olevole.ru
* proler@gmail.com
* sergey@migsoft.com.ua
* sobomax
* spam@rm-rf.kiev.ua
* stas
* tobez
* tremere@cainites.net
* vanilla
* vanilla@
* wen@FreeBSD.org
* wenheping<wenheping@gmail.com>
* wolman@cs.washington.edu
* # Created by Kevin Bowling <kbowling@FreeBSD.org>
* # Created by Matthias Fechner <mfechner@FreeBSD.org>
With hat: portmgr
d076ad9 | |
Monday, 23 May 2022
|
10:46 Palle Girgensohn (girgen)
postgresql??-server: fix regression in the rc script
The rc script was converted to use a SUB_LIST variable, but I failed to
introduce the variable correctly in the Makefile. [1]
The plist for postgresql15-server was incorrect. Fixed this as well.
PR: 264097 [1]
9230d75 | |
Thursday, 12 May 2022
|
13:41 Palle Girgensohn (girgen)
databases/postgresql??-server: update to latest version
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 14.3, 13.7, 12.11, 11.16,
and 10.21. This release fixes over 50 bugs reported over the last three
months. This release closes one security vulnerability and fixes over 50
bugs reported over the last three months.
We encourage you to install this update at your earliest possible
convenience.
If you have any GiST indexes on columns using the ltree data type, you
will need to reindex them after upgrading.
For the full list of changes, please review the release notes.
It also fixes a security issue, CVE-2022-1552:
Autovacuum, REINDEX, and others omit "security restricted operation" sandbox.
Versions Affected: 10 - 14. The security team typically does not test
unsupported versions, but this problem is quite old.
Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER,
and pg_amcheck made incomplete efforts to operate safely when a
privileged user is maintaining another user's objects. Those commands
activated relevant protections too late or not at all. An attacker
having permission to create non-temp objects in at least one schema
could execute arbitrary SQL functions under a superuser identity.
While promptly updating PostgreSQL is the best remediation for most
users, a user unable to do that can work around the vulnerability by
disabling autovacuum, not manually running the above commands, and not
restoring from output of the pg_dump command. Performance may degrade
quickly under this workaround. VACUUM is safe, and all commands are fine
when a trusted user owns the target object.
Security: 157ce083-d145-11ec-ab9b-6cc21735f730
Release notes: https://www.postgresql.org/docs/release/
6c00f6e | |
Thursday, 7 Apr 2022
|
00:39 Jan Beich (jbeich)
devel/icu: update to 71.1
Changes: https://github.com/unicode-org/icu/releases/tag/release-71-1
Reported by: GitHub (watch releases)
PR: 262654
Exp-run by: antoine
Approved by: fluffy
268cee3 | |
Thursday, 10 Feb 2022
|
14:17 Palle Girgensohn (girgen)
databases/postgresql??-server: Upgrade to latest version
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/
7acb062 | |
Thursday, 11 Nov 2021
|
14:37 Palle Girgensohn (girgen)
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/
d3db763 | |
Thursday, 28 Oct 2021
|
16:37 Jan Beich (jbeich)
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
f34ece3 | |
Thursday, 12 Aug 2021
|
16:23 Palle Girgensohn (girgen)
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
a271b9d | |
Tuesday, 27 Jul 2021
|
20:06 Li-Wen Hsu (lwhsu)
databases/postgresql10-server: Fix typo in rc script
PR: 257447
Reported by: Tom Warnke <tom@toromtomtom.com>
MFH: 2021Q3
eae54f6 | |
Tuesday, 1 Jun 2021
|
13:59 Palle Girgensohn (girgen)
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
8d831eb | |
Thursday, 20 May 2021
|
14:38 Palle Girgensohn (girgen)
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.
fccc45e | |
Saturday, 15 May 2021
|
09:12 Palle Girgensohn (girgen)
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/
ab83f2b | |
Thursday, 8 Apr 2021
|
23:33 Jan Beich (jbeich)
devel/icu: update to 69.1
Changes: https://github.com/unicode-org/icu/releases/tag/release-69-1
Reported by: GitHub (watch releases)
69d24a7 | |
Tuesday, 6 Apr 2021
|
14:31 Mathieu Arnold (mat)
Remove # $FreeBSD$ from Makefiles.
305f148 | |
Thursday, 11 Feb 2021
|
14:34 girgen
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
  | |
Thursday, 12 Nov 2020
|
15:00 girgen
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
| |
Tuesday, 3 Nov 2020
|
00:56 jbeich
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)
| |
Thursday, 24 Sep 2020
|
13:33 girgen
Welcome PostgreSQL 13
Release notes: https://www.postgresql.org/about/news/2077/
| |
Thursday, 13 Aug 2020
|
13:45 girgen
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
| |
Sunday, 17 May 2020
|
20:37 girgen
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]
| |
Thursday, 23 Apr 2020
|
20:14 jbeich
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)
| |
Friday, 13 Mar 2020
|
09:54 jbeich
Fix up PORTREVISION style after "portedit bump-revision"
|
09:47 jbeich
devel/icu: update to 66.1
Changes: http://site.icu-project.org/download/66
ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/
| |
Thursday, 13 Feb 2020
|
19:14 girgen
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
| |
Thursday, 14 Nov 2019
|
16:24 girgen
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/
| |
Thursday, 3 Oct 2019
|
20:35 jbeich
devel/icu: update to 65.1
Changes: http://site.icu-project.org/download/65
ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/
| |
Thursday, 8 Aug 2019
|
15:33 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.
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.
| |
Friday, 26 Jul 2019
|
20:46 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
| |
Thursday, 27 Jun 2019
|
21:28 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
| |
Thursday, 9 May 2019
|
22:32 girgen
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]
| |
Thursday, 25 Apr 2019
|
18:34 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
| |
Wednesday, 27 Mar 2019
|
21:11 jbeich
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
| |
Friday, 15 Feb 2019
|
15:45 girgen
Fix mistake in previous commit about postgres username
|
11:02 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
`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]
| |
Wednesday, 12 Dec 2018
|
01:35 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
| |
Monday, 12 Nov 2018
|
15:54 girgen
Fix build problems on i386
Use GCC seems to be proper way to do it. SSE2 would not be available for all
CPU:s.
| |
Thursday, 8 Nov 2018
|
23:21 girgen
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
| |
Tuesday, 23 Oct 2018
|
11:35 jbeich
devel/icu: update to 63.1
Changes: http://site.icu-project.org/download/63
ABI: https://abi-laboratory.pro/tracker/timeline/icu4c/
PR: 232300
Exp-run by: antoine
| |
Monday, 10 Sep 2018
|
13:14 mat
Add DOCS options to ports that should have one.
Also various fixes related to said option.
PR: 230864
Submitted by: mat
exp-runs by: antoine
| |
Friday, 10 Aug 2018
|
09:25 girgen
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
| |
Friday, 29 Jun 2018
|
14:22 jbeich
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)
| |
Friday, 11 May 2018
|
13:10 girgen
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.
| |
Friday, 6 Apr 2018
|
15:53 jbeich
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)
| |
Thursday, 1 Mar 2018
|
15:10 girgen
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
| |
Thursday, 15 Feb 2018
|
14:41 brnrd
security/openssl-devel: Remove BROKEN from some ports
* databases/freetds: Fixed 2017-02-14
* databases/postgresql10-server: Fixed 2016-09-15 [1]
* ftp/lftp: Fixed in 4.8.0
* ftp/proftpd: Fixed in 1.3.5c
* ftp/wget: Fixed in 1.19.3 [2]
* lang/erlang-runtime20: Fixed in 20.0
* net/socat: Fixed in 1.7.3.2
* security/libssh2: Fixed in 1.8.0 [3]
* security/p5-Crypt-OpenSSL-X509: Fixed in 1.8.8
* sysutils/bacula9-server: Fixed in 9.0.6
* www/nginx: Fixed in 1.9.14
* Bulk build OK 10.3/11.1 both i386 and amd64:
- multimedia/librtmp
- net/libvncserver
- www/lynx
PR: 225875 [1], 225872 [2], 225873 [3]
| |
Thursday, 8 Feb 2018
|
19:58 antoine
Remove DTRACE from OPTIONS_DEFAULT, causes segmentation fault during build
With hat: portmgr
|
17:38 girgen
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
| |
Tuesday, 30 Jan 2018
|
13:45 mat
Fix ICU depend for postgresql10-server.
PR: 225049
Submitted by: mat
Approved by: maintainer timeout
Sponsored by: Absolight
| |
Wednesday, 20 Dec 2017
|
22:09 girgen
Fix problem with logical replication
PR: 224466
| |
Thursday, 9 Nov 2017
|
16:11 girgen
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/
| |
Sunday, 8 Oct 2017
|
16:39 girgen
PostgreSQL has renamed wal as xlog to avoid human errors.
This has caused some binaries to change names. Fix the port so they will be
installed again with their new names.
Noticed by: VoidChicken@gmail.com
PR: 222864
| |
Thursday, 5 Oct 2017
|
13:39 girgen
PostgreSQL 10 Released!
Some highlights:
Logical Replication - A publish/subscribe framework for distributing data
Declarative Table Partitioning - Convenience in dividing your data
Improved Query Parallelism - Quickly conquer your analysis
Quorum Commit for Synchronous Replication - Distribute data with confidence
SCRAM-SHA-256 authentication - Secure your data access
URL: https://www.postgresql.org/about/news/1786/
| |
Sunday, 24 Sep 2017
|
18:58 girgen
Correct default data directory for postgresql 10
...and make sure not to bump portrevision more than necessary.
POINTED OUT BY: Peter Laursen
| |
Thursday, 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
| |
Thursday, 10 Aug 2017
|
14:23 girgen
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: 64 |
|
As an Amazon Associate I earn from qualifying purchases.