| Commit message (Collapse) | Author | Files | Lines |
|---|
|
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]
|
|
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
|
|
...and make sure not to bump portrevision more than necessary.
POINTED OUT BY: Peter Laursen
|
|
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/
|
|
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.
|
|
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.
|
|
|
|
Please read the entry from 20160905 in UPDATING:
daemon user has changed to `postgres'
ICU is default on
|
|
- re-assign LOCALBASE to PREFIX
- add PG_GROUP to SUB_PLIST for packaging fix
- fix permissions for package installations
PR: ports/162776
Submitted by: jgh, Phil Phillips < pphillips at experts-exchange.com >
Reviewed by: rene (mentor)
Approved by: crees (maintainer, mentor)
|
|
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
|
|
See http://www.postgresql.org/about/news.1313 for more info.
Also, use USERS knob instead of explicitally creating the pgsql user
while still accepting alternative names, using [1] with some added
magic.
PR: 157667 [1]
|
|
This update contains a critical fix to the pg_upgrade utility
which prevents significant downtime issues. Do not use
pg_upgrade without installing this update first.
The issue with pg_upgrade and the fix are detailed on the PostgreSQL
wiki: http://wiki.postgresql.org/wiki/20110408pg_upgrade_fix
Users who have already used pg_upgrade should run the database repair
script given on that page on their databases as soon as possible.
See the release notes for each version at
http://www.postgresql.org/docs/current/static/release.html for a full
list of changes with details.
Allow the username of the postgresql user to configurable for 8.4 and 9.0.
Largely inspired by the work of Jason Helfman [153668, 153136].
Change PGUSER knob to PG_USER not to clash with PGUSER environment.
PR: 153668, 153136, 155493, 155137
|
|
s#. %%RC_SUBR%%#. /etc/rc.subr#
|
|
propogated by copy and paste.
1. Primarily the "empty variable" default assignment, which is mostly
${name}_flags="", but fix a few others as well.
2. Where they are not already documented, add the existence of the _flags
(or other deleted empties) option to the comments, and in some cases add
comments from scratch.
3. Replace things that look like:
prefix=%%PREFIX%%
command=${prefix}/sbin/foo
to just use %%PREFIX%%. In many cases the $prefix variable is only used
once, and in some cases it is not used at all.
4. In a few cases remove ${name}_flags from command_args
5. Remove a long-stale comment about putting the port's rc.d script in
/etc/rc.d (which is no longer necessary).
No PORTREVISION bumps because all of these changes are noops.
|
|
Release notes:
http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-17
http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-15
http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-10
http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-6
http://www.postgresql.org/docs/8.2/static/release-8-2-1.html
The server-side utilities of postgresql (initdb, initlocation,
ipcclean, pg_controldata, pg_ctl, pg_id and pg_resetxlog) are now
installed by the respective postgresql*-server port (previously they
where installed with the client). If you update the client, you should
also update the server to make sure you are not left without the
server-side tools. Do something like:
portupgrade postgresql-client postgresql-server
|
|
PostgreSQL 8.2.0
Complete release notes are available at
http://www.postgresql.org/docs/current/static/release-8-2.html
|
|
Release notes:
8.1.5 http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-5
8.0.9 http://www.postgresql.org/docs/8.0/static/release.html#RELEASE-8-0-9
7.4.14 http://www.postgresql.org/docs/7.4/static/release.html#RELEASE-7-4-14
7.3.16 http://www.postgresql.org/docs/7.3/static/release.html#RELEASE-7-3-16
Change name of the rc script from '010.pgsql.sh' to 'postgresql'
Add optional hierachy patch added for 7.4 and 8.1 ports.
Chase heimdal libs update [reported by several]
For 8.1+ the port enables autovacuum in ~pgsql/postgresql.conf when
running initdb
Cleanup the ports, moving pkg-message-* to files/pkg-message-*.in and
files/pgsql.sh.tmpl to files/postgresql.in. [ports/97767]
PR: ports/97767, submitted by delphij@FreeBSD.org
|
|
The PostgreSQL Global Development Group today released versions 8.1.4, 8.0.8,
7.4.13 and 7.3.15. This is an urgent update to close a security hole which
can permit a SQL injection attack on some applications running PostgreSQL.
Users are urged to apply the update as soon as reasonably possible. Since the
update affects client functionality, most driver projects will be updating
this week as well.
Because the security issue involved is complex, we have added a section in
Techdocs to explain it: http://www.postgresql.org/docs/techdocs.52. Please
read this first before applying the updates.
Also, fix rc_subr startup problems on FreeBSD-7.x.
Security: http://www.postgresql.org/docs/techdocs.50
PR: ports/95154
|
|
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.
|
|
"start" when booting, since there's no need waste time checking for
running processes when the OS is starting up.
Bumping portrevision.
PR: 90884
Submitted by: Victor Snezhko <snezhko@indorsoft.ru>
|
|
add support to select login class for running postgresql [2].
The new startup script, using rc.subr, is now installed for all
versions of postgresql. Bump portrevisions, since startup script is
modified.
PR: 78630 [1]
Submitted by: Vivek Khera [1]
Submitted by: Brian B. [2]
Approved by: seanc (implicit)
|
|
port (files/pgsql.sh.tmpl) lacks a parameter in the
restart option, causing logs to be send to stdout,
instead of the log file.
Submitted by: Fernando Schapachnik <fernando@mecon.gov.ar>
Approved by: maintainer
PR: 53142
Approved by: fjoe (implicit)
|
|
security, and feature additions. Reduce diffs between postgresql-devel
port. Re-initdb required when upgrading from previous release. See
release notes for details.
Schemas added are system catalogs updated. ::braces for impact::
http://developer.postgresql.org/docs/postgres/release.html#RELEASE-7-3-1
PR: ports/46701
Submitted by: girgen@pingpong.net
|
|
PR: 36975
Submitted by: maintainer
|
|
* Pass the -s option to pg_ctl, to avoid clobbering the display.
It will show error messages only.
* Echo the port name after shutdown.
No functional changes, no PORTREVISION.
|
|
* Move the call to configure.postgresql7 from pre-fetch to pre-extract, so it
won't hang while performing batch fetch operations (like portupgrade -F)
* Add some TCL related files to pkg-plist.tcl, and add a PLIST_SUB in the
Makefile to register the correct tcl version in the plist.
* Do not start postgresql if the database directory does not exist: the
startup sequence could hang because of this.
* Use the "-s" option when starting postgresql with pg_ctl, so it won't
display informational messages. Display only the port name, as do other
packages startup scripts.
Approved by: Palle Girgensohn <girgen@partitur.se>
|
|
PR: ports/26741
Submitted by: maintainer
|
|
PR: 23371
Submitted by: maintainer
|
|
Obtained from: Palle Girgensohn <girgen@partitur.se>
|
|
thanks for complete diffs ;-)
closed PR
PR: 18699
Obtained from: Palle Girgensohn <girgen@partitur.se>
|
|
|
|
maintenance release with bugfixes
Thanks for the complete submission !
Submitted by: Palle Girgensohn <girgen@partitur.se>
|
|
Many bugfixes and cosmetic changes
Changes by Scrappy and me
My additional changes:
- had to link libpgtcl.so with the crypt library to get rid of the
pgaccess error message, that crypt is missing
- had to add -i option in the startup script, so that pgaccess is
able to connect to the postmaster process
- removed all unnecessary patches
- updated PLIST
Thanks to the postgresql developement team, who did a great job to
simplify the postgresql port, by applying the patches and making
the autoconf mechanism more consistent.
Submitted by: The Hermit Hacker <scrappy@hub.org>
|
|
background because of the -S option.
- remove the -D datadir option, it's meaningless, because the pgsql
user environment overwrites it with the PGDATA env variable.
Since this is important and might cause some headache, I mentioned
this in ~pgsql/.profile and the startup script.
Submitted by: John Fiber
|
|
|
|
Please note: when performing a migration to 6.2 and you have an existing db,
then you have to use the *new* pg_dumpall script that comes with this new
postgresql release. The INSTALL file points this out explicitely !!!
Changes:
- startup script resides in FILESDIR
- renamed it to be in sync with INSTALL file from sources
- always install this startup script over an existing, because
of the nature of the rc.d directory I can't install it
to pgsql.sh-dist, if a pgsql.sh is already presend ...
- portlint detected trailing whitespace, usage of perl with absolute
path, usage of echo instead of ECHO and plenty things of this kind
- post installation notes updated, mentioned the mailing list
- copies the html pages as well to the share/doc directory (new manual dir)
- had to update PLIST
- shortened DESCR file, to match the 24 lines
- added post build target, that reminds the admin how to proceed when
already having a database -> INSTALL file describes migration
- updated manpages
|
