PostgreSQL is een open source relational database management system, dat op diverse besturingssystemen kan worden gedraaid. Hierdoor is het breed inzetbaar in verschillende omgevingen. De ontwikkelaars hebben weer een reeks nieuwe versies uitgebracht, met 10.4, 9.6.9, 9.5.13, 9.4.18 en 9.3.23 als versienummers. Gebruikers van oudere uitgaven wordt aangeraden om te upgraden. De bijbehorende aankondiging van PostgreSQL ziet er als volgt uit:
PostgreSQL 10.4, 9.6.9, 9.5.13, 9.4.18, and 9.3.23 released!
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.
Please note that PostgreSQL changed its versioning scheme with the release of version 10.0, so updating to version 10.4 from 10.0, 10.1, 10.2, or 10.3 is considered a minor update.
One security vulnerability has been closed by this release:
Bug Fixes and Improvements
- CVE-2018-1115: Too-permissive access control list on function pg_logfile_rotate()
Please see the "Updating" section below for post-update steps.
This update also fixes over 50 bugs reported in the last several months. Some of these issues affect only version 10, but many affect all supported versions. These fixes include:
This update also contains tzdata release 2018d, with updates for Palestine and Antarctica (Casey Station), plus historical corrections for Portugal and its colonies, as well as Enderbury, Jamaica, Turks & Caicos Islands, and Uruguay.
- Fix incorrect volatility and parallel-safety markings on several built-in functions to ensure correct query planning optimizations
- Several fixes for partitioning, including potential crashes as well as allowing TRUE and FALSE to be used as partition bounds
- Fix where a new TOAST value could be assigned to a dead-but-not-yet-vacuumed TOAST OID, which would result in an error similar to "unexpected chunk number 0 (expected 1) for toast value nnnnn"
- Fix "CREATE TABLE ... LIKE" with bigint identity columns on 32-bit platforms
- Fix memory leak within the runtime of a query that repeatedly executes hash joins
- Several crash fixes around queries using GROUPING SET
- Avoid failure if a query-cancel or session-termination interrupt occurs while committing a prepared transaction
- Reduce locking during autovacuum worker scheduling, which prevents loss of potential worker concurrency
- Fix possible slow execution of REFRESH MATERIALIZED VIEW CONCURRENTLY
- Several fixes around query plans that use "index-only" scans
- Avoid deadlocks in concurrent CREATE INDEX CONCURRENTLY commands that are run under SERIALIZABLE or REPEATABLE READ transaction isolation
- Several fixes for SP-GiST indexes, including one collation-aware searches on text columns
- Fixes related to counting the number of tuples in partial GiST, SP-GiST, and Bloom indexes
- Several fixes for logical decoding and replication
- Fix misquoting of values for list-valued GUC variables (e.g. local_preload_libraries, session_preload_libraries, shared_preload_libraries, temp_tablespaces) in dumps
- Several fixes for pg_stat_activity
- Several fixes for ecpg
- Fix for pg_recvlogical to ensure compatibility with PostgreSQL versions released before 10
- Several fixes for pg_rewind