Up to [cvs.NetBSD.org] / pkgsrc / databases / postgresql92-client
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Removed (jdbc-)postgresql92(-*)
Bump PKGREVISION of postgresql92 and postgresql93 packages (all to 1) for the PR 52787 options adjustment, as a precaution.
postgresql: updated to the latest 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. All users using the affected versions of PostgreSQL should update as soon as possible. If you use BRIN indexes or contrib/start-scripts, please see the release notes for additional post-upgrade steps. Security Issues Three security vulnerabilities have been fixed by this release: CVE-2017-12172: Start scripts permit database administrator to modify root-owned files CVE-2017-15098: Memory disclosure in JSON functions CVE-2017-15099: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges Bug Fixes and Improvements This update also fixes a number of bugs reported in the last few months. Some of these issues affect only version 10, but many affect all supported versions: Fix a race condition in BRIN indexing that could cause some rows to not be included in the indexing. Fix crash when logical decoding is invoked from a PL language function. Several fixes for logical replication. Restored behavior for CTEs attached to INSERT/UPDATE/DELETE statements to pre-version 10. Prevent low-probability crash in processing of nested trigger firings. Do not evaluate an aggregate function's argument expressions when the conditions in the FILTER clause evaluate to FALSE. This complies with SQL-standard behavior. Fix incorrect query results when multiple GROUPING SETS columns contain the same simple variable. Fix memory leak over the lifespan of a query when evaluating a set-returning function from the target list in a SELECT. Several fixes for parallel query execution, including fixing a crash in the parallel execution of certain queries that contain a certain type of bitmap scan. Fix json_build_array(), json_build_object(), jsonb_build_array(), and jsonb_build_object() to handle explicit VARIADIC arguments correctly. Prevent infinite float values from being casted to the numeric type. Fix autovacuum's “work item” logic to prevent possible crashes and silent loss of work items. Several fixes for VIEWs around adding columns to the end of a view. Fix for hashability detection of range data types that are created by a user. Improvements on using extended statistics on columns for the purposes of query planning. Prevent idle_in_transaction_session_timeout from being ignored when a statement_timeout occurred earlier. Fix low-probability loss of NOTIFY messages due more than 2 billion transactions processing before any queries are executed in the session. Several file system interaction fixes. Correctly restore the umask setting when file creation fails in COPY or lo_export(). Fix pg_dump to ensure that it emits GRANT commands in a valid order. Fix pg_basebackup's matching of tablespace paths to canonicalize both paths before comparing to help improve Windows compatibility. Fix libpq to not require user's home directory to exist when trying to read the "~/.pgpass" file. Several fixes for ecpg.
Make sure the --as-needed linker arg does not leak into the pgxs Makefiles on Darwin and SunOS where it's not supported. Bump PKGREVISION on *-client.
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and 9.1.21. This release fixes two security issues and one index corruption issue in version 9.5. It also contains a variety of bug fixes for earlier versions. Users of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible. This release closes security hole CVE-2016-2193, where a query plan might get reused for more than one ROLE in the same session. This could cause the wrong set of Row Level Security (RLS) policies to be used for the query. The update also fixes CVE-2016-3065, a server crash bug triggered by using pageinspect with BRIN index pages. Since an attacker might be able to expose a few bytes of server memory, this crash is being treated as a security issue.
Bump PKGREVISION for security/openssl ABI bump.
Changes: This update fixes CVE-2014-0060, in which PostgreSQL did not properly enforce the WITH ADMIN OPTION permission for ROLE management. This update also fixes some issues which affect binary replication and row locking, and can cause recoverable data corruption in some cases. In addition to the above, the following issues are fixed in this release: Fix WAL logging of visibility map change Make sure that GIN indexes log all insertions Get pause_at_recovery_target to pause at correct time Ensure walreceiver sends hot-standby feedback messages on time Prevent timeout interrupts from taking control away from mainline code Eliminate several race conditions Fix some broken HINTs in error messages Prevent server lockup on SSL connection loss Fix two Unicode handling issues Prevent crash on certain subselect syntax Prevent crash on select from zero column table Fix two bugs with LATERAL Fix issue with UNION ALL, partitioning, and updates Ensure that ANALYZE understands domains over ranges Eliminate permissions check when using default tablespace Fix memory leakage in JSON functions Allow extensions with event triggers Distinguish numbers correctly in JSON output Fix permissions for pg_start_backup() and pg_stop_backup() Accept SHIFT_JIS as locale name Fix .* expansion for SQL function variables Prevent infinite loop on some COPY connection failures Several fixes for client issues on Windows Enable building PostgreSQL with Visual Studio 2013 Update time zone files for recent changes
Recursive PKGREVISION bump for OpenSSL API version bump.
Now all of the postgresql packages should compile on MirBSD.
The PostgreSQL Global Development Group has released a security update to all current versions of the PostgreSQL database system, including versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, and 8.3.23. This update fixes a denial-of-service (DOS) vulnerability. All users should update their PostgreSQL installations as soon as possible. The security issue fixed in this release, CVE-2013-0255, allows a previously authenticated user to crash the server by calling an internal function with invalid arguments. This issue was discovered by independent security researcher Sumit Soni this week and reported via Secunia SVCRP, and we are grateful for their efforts in making PostgreSQL more secure. Today's update also fixes a performance regression which caused a decrease in throughput when using dynamic queries in stored procedures in version 9.2. Applications which use PL/pgSQL's EXECUTE are strongly affected by this regression and should be updated. Additionally, we have fixed intermittent crashes caused by CREATE/DROP INDEX CONCURRENTLY, and multiple minor issues with replication. This release is expected to be the final update for version 8.3, which is now End-of-Life (EOL). Users of version 8.3 should plan to upgrade to a later version of PostgreSQL immediately. For more information, see our Versioning Policy. This update release also contains fixes for many minor issues discovered and patched by the PostgreSQL community in the last two months, including: * Prevent unnecessary table scans during vacuuming * Prevent spurious cached plan error in PL/pgSQL * Allow sub-SELECTs to be subscripted * Prevent DROP OWNED from dropping databases or tablespaces * Make ECPG use translated messages * Allow PL/Python to use multi-table trigger functions (again) in 9.1 and 9.2 * Fix several activity log management issues on Windows * Prevent autovacuum file truncation from being cancelled by deadlock_timeout * Make extensions build with the .exe suffix automatically on Windows * Fix concurrency issues with CREATE/DROP DATABASE * Reject out-of-range values in to_date() conversion function * Revert cost estimation for large indexes back to pre-9.2 behavior * Make pg_basebackup tolerate timeline switches * Cleanup leftover temp table entries during crash recovery * Prevent infinite loop when COPY inserts a large tuple into a table with a large fillfactor * Prevent integer overflow in dynahash creation * Make pg_upgrade work with INVALID indexes * Fix bugs in TYPE privileges * Allow Contrib installchecks to run in their own databases * Many documentation updates * Add new timezone "FET".
PKGREVISION bumps for the security/openssl 1.0.1d update.
recursive bump from cyrus-sasl libsasl2 shlib major bump.
The PostgreSQL Global Development Group announces PostgreSQL 9.2, the latest release of the leader in open source databases. Since the beta release was announced in May, developers and vendors have praised it as a leap forward in performance, scalability and flexibility. Users are expected to switch to this version in record numbers. PostgreSQL 9.2 will ship with native JSON support, covering indexes, replication and performance improvements, and many more features. We are eagerly awaiting this release and will make it available in Early Access as soon as it’s released by the PostgreSQL community," said Ines Sombra, Lead Data Engineer, Engine Yard.