non port: Mk/Uses/pgsql.mk |
Number of commits found: 44 |
Sunday, 31 Dec 2023
|
00:06 Muhammad Moinur Rahman (bofh)
databases/postgresql11: Sunset
bbd8259 |
Wednesday, 5 Jul 2023
|
14:11 Palle Girgensohn (girgen)
databases/postgresql16-*: Introduce postgresql16 beta 1
URL: https://www.postgresql.org/about/news/postgresql-16-beta-1-released-2643/
Release notes: https://www.postgresql.org/docs/16/release-16.html
4ee225f |
Saturday, 15 Apr 2023
|
13:14 Muhammad Moinur Rahman (bofh)
*/*: Remove pointers to EOLed pgsql versions
- Remove dotted pgsql versions
Approved by: portmgr
a40c0e7 |
Tuesday, 7 Mar 2023
|
21:15 Rene Ladan (rene)
Mk: unregister expired PostgreSQL 10
47c9ea7 |
Thursday, 19 May 2022
|
13:36 Palle Girgensohn (girgen)
databases/postgresql??-*: add postgresql-15 to the ports tree
Introduce PostgreSQL-15 to the ports tree.
Make version 15 the master port, and add plist parameter for the
postgresql version.
Release notes: https://www.postgresql.org/docs/devel/release.html
5b11f47 |
Sunday, 24 Apr 2022
|
10:00 Tobias C. Berner (tcberner)
framework: cleanup conditional-indentations in Mk/
Run Tools/scripts/indent_make_if.pl on all of Mk.
These white space changes contribute greatly to the readability of those files.
As we have a version control system, finding out the reasons for the changes
prior to these white space changes is still easily possible
Differential Revision: https://reviews.freebsd.org/D35024
Reviewed by: portmgr (rene, bapt)
aa25396 |
Friday, 11 Mar 2022
|
11:30 Rene Ladan (rene)
Mk: unregister expired PostgreSQL 9.6
Update an IGNORE message, leave examples at the top of pgsql.mk
alone for now.
a444293 |
Monday, 14 Jun 2021
|
14:12 Sergey A. Osokin (osa)
Mk/Uses: remove 9.5 from the VALID_PGSQL_VER list.
Fixes: a3da90c5e4f183d6a61b55ac6da01974ab575ed1
Approved by: portmgr (rene)
7aac8c2 |
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 |
Tuesday, 6 Apr 2021
|
14:27 Mathieu Arnold (mat)
framework: Remove $FreeBSD$
Where appropriate fiddle with a few other things.
5d33e04 |
Thursday, 24 Sep 2020
|
13:33 girgen
Welcome PostgreSQL 13
Release notes: https://www.postgresql.org/about/news/2077/
|
Friday, 24 Jul 2020
|
16:59 rene
Mk: unregister expired PostgreSQL 9.4
|
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.
|
Tuesday, 15 Jan 2019
|
21:50 crees
Add facility to give a range of allowable versions for postgresql
PR: ports/213038
PR: ports/234813
Submitted by: lbartoletti@tuxfamily.org
Differential Revision: https://reviews.freebsd.org/D18818
|
Monday, 14 Jan 2019
|
13:45 mat
9.3 has been removed.
Reported by: sbruno
|
Thursday, 20 Dec 2018
|
18:36 crees
Add -plpython capability
PR: ports/222094
Submitted by: lbartoletti@tuxfamily.org
|
Friday, 19 Oct 2018
|
21:32 girgen
The PostgreSQL Global Development Group today announced the release of
PostgreSQL 11, the latest version of the world's most advanced open
source database.
PostgreSQL 11 provides users with improvements to overall performance of
the database system, with specific enhancements associated with very
large databases and high computational workloads. Further, PostgreSQL 11
makes significant improvements to the table partitioning system, adds
support for stored procedures capable of transaction management,
improves query parallelism and adds parallelized data definition
capabilities, and introduces just-in-time (JIT) compilation for
accelerating the execution of expressions in queries.
"For PostgreSQL 11, our development community focused on adding features
that improve PostgreSQL's ability to manage very large databases," said
Bruce Momjian, a core team member of the PostgreSQL Global Development
Group. "On top of PostgreSQL's proven performance for transactional
workloads, PostgreSQL 11 makes it even easier for developers to run big
data applications at scale."
PostgreSQL benefits from over 20 years of open source development and
has become the preferred open source relational database for developers.
The project continues to receive recognition across the industry, and
has been featured as the "DBMS of the Year 2017" by DB-Engines and in
the SD Times 2018 100.
PostgreSQL 11 is the first major release since PostgreSQL 10 was
released on October 5, 2017. The next update release for PostgreSQL 11
containing bug fixes will be PostgreSQL 11.1, and the next major release
with new features will be PostgreSQL 12.
Release Notes: https://www.postgresql.org/docs/11/static/release-11.html
|
Saturday, 10 Feb 2018
|
22:19 rene
Remove Postgresql 9.2 from the list of supported versions.
Submitted by: cmt
|
Thursday, 10 Aug 2017
|
20:25 girgen
Add PostgreSQL-10 to the ports tree
|
Monday, 3 Oct 2016
|
18:15 rene
Unregister databases/postgresql91 and mention postgresql96 as a valid version.
Submitted by: myself
Reviewed by: mat
Differential Revision: https://reviews.freebsd.org/D8123
|
Monday, 5 Sep 2016
|
11:15 girgen
Add PostgreSQL-9.6 RC1
Please read the entry from 20160905 in UPDATING:
daemon user has changed to `postgres'
ICU is default on
|
Wednesday, 3 Aug 2016
|
12:09 mat
Always include bsd.default-versions.mk in bsd.port.mk.
The variable defined in it are now always available after including
bsd.port.pre.mk.
PR: 210666
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D6933
|
Friday, 1 Jul 2016
|
17:45 matthew
Delete the now expired postgresql90 ports. Upstream support for
postgresql-9.0.x was declared EoL in September 2015.
Summary:
Remove 9.0 from the list of postgresql versions available in ports
Disconnect postgresql90 ports from the build
Remove postgresql90-pgtcl port
Remove postgresql90-client port
Move the master postgreslXY-plperl makefile to postgresql95-plperl/Makefile.
Adjust include lines in other postgresqlXY-plperl ports
Delete postgresql90-plperl
Move the master postgreslXY-plpython/{Makefile,pkg-descr} to
postgresl95-plpython/{Makefile,pkg-descr}
Adjust all other postgresqlXY-plpython/Makefile to include the new master
Remove postgresql90-server
Reviewers: jgh, girgen, #portmgr, O5 Ports Framework, bapt, crees
Reviewed By: #portmgr, O5 Ports Framework, bapt, crees
Subscribers: mat
Differential Revision: https://reviews.freebsd.org/D6898
|
Wednesday, 22 Jun 2016
|
06:27 matthew
WANT_PGSQL=lib adds a LIB_DEPENDS on postgresglXY-client (this is also
the default when WANT_PGSQL is not defined). Compare to
WANT_PGSQL=client which only adds a RUN_DEPENDS on
postgresqlXY-client. 'client' can be part of a list of different
components, but 'lib' is ignored if any other terms are specified,
which seems an arbitrary and incorrect restriction.
WANT_PGSQL=lib allows expressing that the port links against
libpq.so.X rather than just needing one of the client programs like
psql(1) at runtime. However, other than that there is little
practical difference between 'lib' and 'client' on the resulting pkg.
Approved by: crees (pgsql@)
Sponsored by: https://reviews.freebsd.org/D6893
|
Thursday, 14 Apr 2016
|
13:34 mat
Try to be more helpful to our users, and keep all the possible versions
close to their default value in Mk/bsd.default-versions.mk.
Sponsored by: Absolight
|
Sunday, 27 Mar 2016
|
01:23 bapt
Remove the now unneeded ${PORTSDIR} from dependency definition in
The infrastructure Makefiles
PR: 206569
Exp run by: antoine
Differential Revision: D5047
|
Thursday, 17 Mar 2016
|
12:09 fjoe
Fix installed version check on FreeBSD 9.
PR: 200569
|
Wednesday, 10 Feb 2016
|
12:18 fjoe
Prefer installed version instead of insisting on using default version.
PR: 200569
|
Friday, 22 Jan 2016
|
00:18 girgen
pgbench has moved from contrib to base in 9.5
so we need something else to depend on for -contrib
|
Thursday, 7 Jan 2016
|
19:58 girgen
The PostgreSQL Global Development Group announces the
release of PostgreSQL 9.5.
This release adds UPSERT capability, Row Level Security,
and multiple Big Data features, which will broaden the
user base for the world's most advanced database.
With these new capabilities, PostgreSQL will be
the best choice for even more applications for startups,
large corporations, and government agencies.
Release Notes:
http://www.postgresql.org/docs/current/static/release-9-5.html
What's New in 9.5:
https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_9.5
|
Thursday, 15 Oct 2015
|
07:36 bapt
Readd PORTSDIR for now we will only start removing them after 2016Q1 is branched
This gives more time for tools to get updated, available in packages etc before
bothering users
|
Wednesday, 14 Oct 2015
|
16:49 bapt
Drop the necessity to add ${PORTSDIR} to dependency line
Modify make describe to automatically prepend ${PORTSDIR} if the path for the
port is not absolute
Checked with poudriere, portmaster, portupgrade
PR: 203685
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D3866
|
Tuesday, 7 Jul 2015
|
21:31 pgollucci
- Fix dependencies on docs, plperl, pltcl
postgresql93-$dep not postgresql9.3-$dep
Note, nothing uses doc, plperl, or pltcl yet
Required for PR: 201124
Approved by: portmgr (bapt)
|
Wednesday, 10 Jun 2015
|
15:36 rene
USES=pgsql: desupport PostgreSQL 8.4
Postgresql 8.4 expired on 2015-05-10 because upstream discontinued support for
them in July 2014.
PR: 200228
Reviewed by: marino, portmgr (antoine)
|
Saturday, 22 Nov 2014
|
21:31 crees
Fix special [:build] case
|
Sunday, 28 Sep 2014
|
16:36 tijl
Change the way USES is handled:
- Loop over USES twice, once to define all *_ARGS variables and once to
include Uses/*.mk. This allows all Uses/*.mk to examine arguments given
to other USES entries.
- Always define *_ARGS (possibly empty) and replace commas with spaces.
Similar for _USES_POST.
Adjust all Uses/*.mk:
- defined(u_ARGS) becomes !empty(u_ARGS)
- Eliminate helper variables like _*_ARGS=${*_ARGS:C/,/ /g}
- Some Uses/*.mk used ":" as argument separator instead of ",", but no port
used this form
- Uses/cran.mk: remove unused variable VALID_ARGS and USES+=fortran which
has no effect
- Uses/twisted.mk: simplify handling of the case where neither "build" nor
"run" arguments have been specified
PR: 193931
Exp-run by: antoine
Approved by: portmgr (antoine)
|
Tuesday, 2 Sep 2014
|
17:53 crees
Complain properly about invalid pgsql default versions.
Please remember you need the period; 9.0 9.1 good, 90 bad, 90+ very bad!
|
Monday, 25 Aug 2014
|
17:53 crees
Convert pgsql ports to use USES+=pgsql
Reviewed by: bapt
|
Thursday, 29 May 2014
|
08:09 antoine
Add 9.4 to the list of valid pgsql versions
With hat: portmgr
|
Tuesday, 27 May 2014
|
10:55 bapt
Fix version comparison
|
Monday, 5 May 2014
|
12:39 bapt
Finish USES=pgsql
Add WANT_PGSQL=client support
Do not test WANT_PGSQL if it is not defined
Fix a couple of typos makeing it unusable
add WANT_PGSQL=lib (default it nothing is specified)
only depends on library if no WANT_PGSQL is set or lib is explicitly
added to WANT_PGSQL
|
Saturday, 15 Mar 2014
|
10:31 gerald
Move MAINTAINER lines to the end of the initial comment block and
make things a bit more consistent.
Approved by: portmgr (bapt)
|
Monday, 13 Jan 2014
|
07:07 bapt
First simple and easy change: use mordern LIB_DEPENDS
|
Sunday, 12 Jan 2014
|
21:16 crees
Strip postgresql code out of bsd.database.mk, and introduce USES=pgsql.
New syntax:
# Depend on postgresql-client
USES= pgsql
# Depend on postgresql-client at least 9.2
USES= pgsql:9.2+
#Depend on postgresql-server at least 9.0
USES= pgsql:9.0+
WANT_PGSQL= server
Postgresql now supports DEFAULT_VERSIONS, and please note that the
version syntax now includes dots(!); i.e. before it was 90, now 9.0
Reviewed by: ade, silence from pgsql@
|
Number of commits found: 44 |