CVE-2016-0773, an issue with regular expression parsing. Various other fixes.
Note: ..."if you are upgrading an installation that contains any GIN
indexes that use the (non-default) jsonb_path_ops operator class, see
the first changelog entry"...
http://www.postgresql.org/docs/current/static/release-9-4-6.html
OK pea@
On OpenBSD, the sa_family field in netmask sockaddrs can be zero and
thus different from the sa_family of the address sockaddr.
Until this glitch gets corrected, fix postgresql.
ok sthen@ pea@ (MAINTAINER)
The incorrect code was generating memcpy calls with src and dest
overlapping, which raises SIGABRT, making the server unreachable
using IPv6. The fix consists in passing the right parameters to
memcpy, including sizeof(struct sockaddr_in) as len, since
sizeof(struct sockaddr_storage) would be too much, and sa_len
is unusable in netmask sockaddrs. Debugged with sthen@ and lteo@
Problem reported by Hugo Osvaldo Barrera.
ok sthen@
cluster, creates a database (optionally), starts server and then starts
actual test code. The server gets correctly shut down after testing.
Also, only Unix sockets are used for connections, minimizing side effects
on running system.
Man page to follow.
okay espie@
"The data corruption issue in PostgreSQL 9.3 affects binary replication
standbys, servers being recovered from point-in-time-recovery backup,
and standalone servers which recover from a system crash. The bug
causes unrecoverable index corruption during recovery due to incorrect
replay of row locking operations. This can then cause query results to be
inconsistent depending on whether or not an index is used, and eventually
lead to primary key violations and similar issues."
ok sthen@, jasper@
This update fixes 8 CVE (CVE-2014-0060, CVE-2014-0061, CVE-2014-0062,
CVE-2014-0063, CVE-2014-0064, CVE-2014-0065, CVE-2014-0066 and CVE-2014-0067).
This update also fixes some issues which affect binary replication and row
locking, and can cause recoverable data corruption in some cases.
ok sthen@
avoiding any issues with it being higher than whatever value openfiles-max
ends up taking (which may be non-obvious as it may be inherited from
"openfiles" in "default"). ok ajacoutot@ pea@
