Softpedia >Mac >Utilities >Postgres.app >  Changelog

Postgres.app Changelog

What's new in Postgres.app 2.7.2

Feb 22, 2024
  • @jakob has created a really nice UI for managing Client App Permissions in the preferences, which also allows you to change decisions later. New connection attempts are now added even if the helper application was unable to show the permission dialog, so this should provide a workaround to (#749).
  • Also, the 2.7.x releases had a bug where disabling "Ask for permission when apps connect without password" was not respected if the server was started automatically on login or from the menu (#752). This release fixes that.

New in Postgres.app 2.7.1 (Feb 9, 2024)

  • This release contains the latest bugfixes for all supported versions of PostgreSQL.

New in Postgres.app 2.7 (Jan 16, 2024)

  • Postgres.app now shows a permission prompt when an app attempts to connect for the first time. For more information, see https://postgresapp.com/documentation/app-permissions.html
  • This release also contains the latest versions of PostGIS and GEOS. The following PostgreSQL versions are available.
  • PostgreSQL 11.22 with PostGIS 2.5.9
  • PostgreSQL 12.17 with PostGIS 3.0.10
  • PostgreSQL 13.13 with PostGIS 3.1.10
  • PostgreSQL 14.10 with PostGIS 3.2.6
  • PostgreSQL 15.5 with PostGIS 3.3.5
  • PostgreSQL 16.1 with PostGIS 3.4.1
  • If you are using PostGIS, remember to run SELECT postgis_extensions_upgrade(); for each PostGIS enabled database to update the extension's SQL definitions.
  • This release also includes a minor bug fix where the app did not activate correctly when opened from the menu item (issue #743).

New in Postgres.app 2.6.8 (Nov 9, 2023)

  • This release contains the latest bugfixes for all supported versions of PostgreSQL.
  • PostgreSQL 16.1 with PostGIS 3.4.0
  • PostgreSQL 15.5 with PostGIS 3.3.4
  • PostgreSQL 14.10 with PostGIS 3.2.5
  • PostgreSQL 13.13 with PostGIS 3.1.9
  • PostgreSQL 12.17 with PostGIS 3.0.9
  • PostgreSQL 11.22 with PostGIS 2.5.9
  • Notable changes since Postgres.app 2.6.7:
  • PostGIS: support for writeable MVT in OGR
  • PostGIS: support for netCDF in GDAL / OGR (#731) with PostgreSQL 16
  • New versions of extensions pgrouting and pgvector. Run ALTER EXTENSION ... UPDATE to update
  • PostgreSQL got several fixes affecting index creation and maintenance. Please check the release notes whether or not your databases may be affected and reindexing would be advisable.
  • Fixed an issue where Postgres.app didn't auto-start when not in /Applications
  • Fixed an issue where Postgres.app didn't launch on macOS 10.13 when not in /Applications

New in Postgres.app 2.6.5 (Aug 11, 2023)

  • This set of releases contains the latest bugfixes for PostgreSQL and includes PostgreSQL 16 Beta 3 with PostGIS 3.4.
  • Additionally, OpenSSL and some PostGIS dependencies got updates and support for several file formats was fixed in OGR (#724)

New in Postgres.app 2.6.4 (Jun 30, 2023)

  • This set of releases includes PostgreSQL 16 Beta 2. We now also include PostGIS again in the beta release!
  • Additionally, PG 15 and PG 16 now come with the extension pgrouting.
  • Additionally, these builds include the latest PostGIS and OpenSSL bugfix releases.

New in Postgres.app 2.6.2 (May 11, 2023)

  • New Features:
  • @tbussmann has been hard at work to include two new extensions with PostgreSQL 15:
  • The pgvector extension is now included (see #716)
  • PostGIS is finally built with support for SFCGAL! (see #337, #529, #685)
  • We've also added a feature to the GUI that allows setting/resetting PostgreSQL user passwords (#718).
  • Bugfixes:
  • This release comes with the quarterly PostgreSQL bug fix releases (15.3, 14.8, 13.11, 12.15, 11.20). See the release notes for details
  • we've added a patch that fixes a problem with pg_basebackup (#715)

New in Postgres.app 2.6.1 (Apr 10, 2023)

  • This release fixes issues #695 and #708

New in Postgres.app 2.5.12 (Nov 10, 2022)

  • This release contains the latest bugfixes for all supported versions of PostgreSQL.
  • This is the final release of PostgreSQL 10. If you still have databases running on PostgreSQL 10, you should consider upgrading your database after installing this update.

New in Postgres.app 2.5.9 (Aug 12, 2022)

  • This release contains the latest bugfixes for PostgreSQL.
  • PostgreSQL 10.22 with PostGIS 2.4.10
  • PostgreSQL 11.17 with PostGIS 2.5.7
  • PostgreSQL 12.12 with PostGIS 3.0.6
  • PostgreSQL 13.8 with PostGIS 3.1.6
  • PostgreSQL 14.5 with PostGIS 3.2.2
  • PostgreSQL 15beta3 with PostGIS 3.3.0rc1
  • It also includes a bugfix for an issue where the app can fail to launch if Rosetta is uninstalled (see #672)

New in Postgres.app 2.5.8 (Jun 17, 2022)

  • This release comes with PostgreSQL 14.4
  • This is an unscheduled release that fixes a bug in PostgreSQL 14 where indexes can become corrupted if you build them concurrently.
  • The only thing that's different is PostgreSQL 14. The other PostgreSQL versions have not been changed.

New in Postgres.app 2.5.7 (May 25, 2022)

  • This release contains the latest bugfix releases of PostgreSQL and PostGIS:
  • PostgreSQL 10.21 with PostGIS 2.4.10
  • PostgreSQL 11.16 with PostGIS 2.5.6
  • PostgreSQL 12.11 with PostGIS 3.0.5
  • PostgreSQL 13.7 with PostGIS 3.1.5
  • PostgreSQL 14.3 with PostGIS 3.2.1
  • The PostgreSQL release notes say you have to reindex GiST indexes on columns of type ltree in PostgreSQL 13 and 14.
  • We've upgraded the version of PostGIS that ships with PostgreSQL 14. If you want to make use of the new features in PostGIS 3.2, make sure to execute SELECT postgis_extensions_upgrade();
  • The GUI now shows a warning if we believe that you have to reindex your databases due to a collation change. See issue #665 for details.
  • Postgres.app now also uses a different method for starting the helper app. I hope this fixes #604 ("PostgresMenuHelper.app is not open anymore")

New in Postgres.app 2.5.6 (Feb 10, 2022)

  • This release contains the latest bugfix releases of PostgreSQL and PostGIS:
  • PostgreSQL 10.20 with PostGIS 2.4.9
  • PostgreSQL 11.15 with PostGIS 2.5.5
  • PostgreSQL 12.10 with PostGIS 3.0.5
  • PostgreSQL 13.6 with PostGIS 3.1.5
  • PostgreSQL 14.2 with PostGIS 3.1.5
  • We no longer include PostgreSQL 9.6, since it has reached end of life in November. If you still have a PostgreSQL 9.6 database running, please update it to a newer version before installing this update.
  • Besides the PostgreSQL bug fixes, this release also fixes two issues with the Postgres.app GUI itself:
  • we fixed issue #639 (Postgres.app shouldn't crash when launching from somewhere other than /Applications).
  • we added -Os to the build flags, which should greatly improve the performance of PostgreSQL (see issue #654)

New in Postgres.app 2.5.2 (Nov 15, 2021)

  • Fixes:
  • We include address_standardizer extension again for all versions of PostgreSQL (see #641 for details).
  • PostgreSQL 13 and 14 now work again on macOS 10.12 (see #643 for details)

New in Postgres.app 2.5.1 (Oct 28, 2021)

  • This is a bugfix release of Postgres.app that fixes a crash when trying to start Intel binaries on Macs with Apple Silicon if Rosetta is not installed (#638)
  • This fix is only relevant for older versions of PostgreSQL. If you just need PG 14, you can continue using Postgres.app 2.5

New in Postgres.app 2.4.4 (Aug 15, 2021)

  • PostgreSQL 9.5.25 with PostGIS 2.2.8
  • PostgreSQL 9.6.23 with PostGIS 2.3.11
  • PostgreSQL 10.18 with PostGIS 2.4.9
  • PostgreSQL 11.13 with PostGIS 2.5.5
  • PostgreSQL 12.8 with PostGIS 3.0.3
  • PostgreSQL 13.4 with PostGIS 3.1.3

New in Postgres.app 2.4.3 (May 19, 2021)

  • PostgreSQL 9.5.25 with PostGIS 2.2.8
  • PostgreSQL 9.6.22 with PostGIS 2.3.11
  • PostgreSQL 10.17 with PostGIS 2.4.9
  • PostgreSQL 11.12 with PostGIS 2.5.5
  • PostgreSQL 12.7 with PostGIS 3.0.3
  • PostgreSQL 13.3 with PostGIS 3.1.1

New in Postgres.app 2.4.1 (Nov 14, 2020)

  • This release contains the November 2020 bugfixes for PostgreSQL 9.5 - 13.

New in Postgres.app 2.3.5 (May 15, 2020)

  • This release contains the querterly updates of PostgreSQL.

New in Postgres.app 2.3.3c (Dec 12, 2019)

  • We removed support for Kerberos (see issues #537, #538, #539)
  • We attempted to fix an issue where Postgres.app could not open Terminal.app (#509)

New in Postgres.app 2.1.5 (Aug 9, 2018)

  • It includes three versions of PostgreSQL:
  • PostgreSQL 9.5.14 with PostGIS 2.2.7
  • PostgreSQL 9.6.10 with PostGIS 2.3.7
  • PostgreSQL 10.5 with PostGIS 2.4.4

New in Postgres.app 2.2 Beta (May 25, 2018)

  • The latest build of Postgres.app with PostgreSQL 11 Beta 1.
  • Also includes a development build of PostGIS 2.5.
  • Requires macOS 10.10 or later.
  • This version does not include plv8, since I couldn't get it to build. I'll try to include plv8 in the next beta.

New in Postgres.app 2.1.4 (May 10, 2018)

  • This release of Postgres.app comes with the latest binaries from the PostgreSQL Quarterly Update May 2018.

New in Postgres.app 2.1.3 (Mar 2, 2018)

  • Ssecurity update which addresses the security vulnerability CVE-2018-1058.

New in Postgres.app 2.1.2 (Feb 14, 2018)

  • It includes three versions of PostgreSQL:
  • PostgreSQL 10.2 (Release Notes) with PostGIS 2.4.3
  • PostgreSQL 9.6.7 (Release Notes) with PostGIS 2.3.6
  • PostgreSQL 9.5.11 (Release Notes) with PostGIS 2.2.6

New in Postgres.app 2.1.1 (Nov 9, 2017)

  • This is the latest and greatest version of Postgres.app for Macs running macOS 10.10 or later.
  • It includes three versions of PostgreSQL:
  • PostgreSQL 10.1 (Release Notes) with PostGIS 2.4.1
  • PostgreSQL 9.6.6 (Release Notes) with PostGIS 2.3.4
  • PostgreSQL 9.5.10 (Release Notes) with PostGIS 2.2.6

New in Postgres.app 2.1 (Oct 5, 2017)

  • This is the latest and greatest version of Postgres.app for Macs running macOS 10.10 or later.
  • It includes three versions of PostgreSQL:
  • PostgreSQL 10.0 (Release Notes) with PostGIS 2.4.0
  • PostgreSQL 9.6.5 (Release Notes) with PostGIS 2.3.3
  • PostgreSQL 9.5.9 (Release Notes) with PostGIS 2.2.5

New in Postgres.app 2.0.5 (Sep 1, 2017)

  • It includes two versions of PostgreSQL:
  • PostgreSQL 9.6.5 (Release Notes) with PostGIS 2.3.3
  • PostgreSQL 9.5.9 (Release Notes) with PostGIS 2.2.5

New in Postgres.app 2.0.4 (Aug 11, 2017)

  • Upgrade to the latest maintenance releases of PostgreSQL.
  • This is the latest and greatest version of Postgres.app for Macs running macOS 10.10 or later. It includes two versions of PostgreSQL:
  • PostgreSQL 9.6.4 (Release Notes) with PostGIS 2.3.3
  • PostgreSQL 9.5.8 (Release Notes) with PostGIS 2.2.5

New in Postgres.app 2.1 Beta 1 (May 19, 2017)

  • Contains PostgreSQL 9.5 and 9.6 so you can try PostgreSQL 10 alongside your existing databases.
  • PostgreSQL 9.6.3 (Release Notes) with PostGIS 2.3.2
  • PostgreSQL 9.5.7 (Release Notes) with PostGIS 2.2.5
  • PostgreSQL 10beta1 (without PostGIS)
  • To try PostgreSQL 10, download the ZIP file, expand it, and drag Postgres.app to your Applications folder. Then create a new server in the sidebar, choosing version 10.

New in Postgres.app 2.0.3 (May 11, 2017)

  • Upgrade to the latest maintenance releases of PostgreSQL!
  • This is the latest and greatest version of Postgres.app for Macs running macOS 10.10 or later. It includes two versions of PostgreSQL:
  • PostgreSQL 9.6.3 (Release Notes) with PostGIS 2.3.2
  • PostgreSQL 9.5.7 (Release Notes) with PostGIS 2.2.5
  • This release also contains two bugfixes:
  • Changed menu icon to use native light/dark mode #385 (thanks to @NickSturgeon)
  • Fixed race condition at system start #386 (thanks to @9mm)

New in Postgres.app 2.0.2 (Feb 9, 2017)

  • This is the latest and greatest version of Postgres.app for Macs running macOS 10.10 or later. It includes two versions of PostgreSQL:
  • PostgreSQL 9.6.2 (Release Notes) with PostGIS 2.3.2
  • PostgreSQL 9.5.6 (Release Notes) with PostGIS 2.2.5
  • In addition, this release also contains minor UI tweaks:
  • configuration files are no longer opened in TextEdit (to avoid typographic quotes) #368
  • the elephant menu now contains "show preferences" and "check for updates" commands #373

New in Postgres.app 2.0.1 (Dec 23, 2016)

  • Feature highlights include:
  • all new UI
  • automatic updates
  • run multiple servers simultaneously
  • The following versions of PostgreSQL are included inside the package:
  • PostgreSQL 9.6.1 (with PostGIS 2.3.1)
  • PostgreSQL 9.5.5 (with PostGIS 2.2.4)
  • Postgres.app 2.0 requires macOS 10.10 or later.
  • Version 2.0.1 fixes a crash on macOS 10.10.

New in Postgres.app 9.6.1.1 (Dec 16, 2016)

  • PostgreSQL 9.6.1
  • PostGIS 2.3.1
  • OpenSSL 1.0.2j
  • This build also includes libpgport and libpgcommon, two static libraries required for building extensions. This should fix and #358 and #360.

New in Postgres.app 2.0 Beta 4 (Dec 16, 2016)

  • bugfix for Stop button #362 (thanks to @ultimate-deej)
  • better error handling when initialising new servers
  • new server settings popover

New in Postgres.app 2.0 Beta 3 (Nov 8, 2016)

  • Includes the following features:
  • bugfix for dark mode #351 (Thanks to @adamhartford)
  • This build includes PostgreSQL 9.6.1 (with PostGIS 2.3) and PostgreSQL 9.5.5 (with PostGIS 2.2.3).

New in Postgres.app 2.0 Beta 2 (Oct 27, 2016)

  • This beta 2 update of Postgres.app includes the following features:
  • display long database names (up to 3 lines of text)
  • fixed issue with menu helper
  • permanently disable login item via preferences
  • This build includes PostgreSQL 9.6.1 (with PostGIS 2.3) and PostgreSQL 9.5.5 (with PostGIS 2.2.3).

New in Postgres.app 9.6.1 (Oct 27, 2016)

  • PostgreSQL 9.6.1
  • PostGIS 2.3.0
  • OpenSSL 1.0.2j

New in Postgres.app 2.0 Beta 1 (Oct 21, 2016)

  • Feature highlights include:
  • all new UI
  • automatic updates
  • run multiple servers simultaneously
  • This build includes PostgreSQL 9.6 (with PostGIS 2.3) and PostgreSQL 9.5.4 (with PostGIS 2.2.2).

New in Postgres.app 2.0 Alpha 1 (Oct 18, 2016)

  • A first alpha build of the all new Postgres.app
  • All new UI
  • Run multiple servers simultaneously
  • Written in Swift 3, requires OS X 10.10 or later
  • This build comes with PostgreSQL 9.6.0. Future builds will contain multiple versions of PostgreSQL

New in Postgres.app 9.6.0 (Sep 30, 2016)

  • PostgreSQL 9.6.0
  • PostGIS 2.3.0
  • plv8 1.4.8
  • OpenSSL 1.0.2j

New in Postgres.app 9.5.4.2 (Sep 9, 2016)

  • PostgreSQL 9.5.4
  • PostGIS 2.2.2
  • plv8 1.4.8
  • OpenSSL 1.0.1t
  • This build adds the address_standardizer extension for PostGIS

New in Postgres.app 9.6 Beta 4.1 (Aug 18, 2016)

  • PostgreSQL 9.6beta4
  • PostGIS 2.2.2
  • plv8 1.4.8
  • OpenSSL 1.0.1t

New in Postgres.app 9.5.4.1 (Aug 17, 2016)

  • PostgreSQL 9.5.4
  • PostGIS 2.2.2
  • plv8 1.4.8
  • OpenSSL 1.0.1t
  • This is a security release. It updates the bundled libxml2 to version 2.9.4

New in Postgres.app 9.5.4.0 (Aug 12, 2016)

  • This is a security release
  • PostGIS 2.2.2
  • plv8 1.4.8
  • OpenSSL 1.0.1t
  • Security Issues:
  • Two security holes have been closed by this release:
  • CVE-2016-5423: certain nested CASE expressions can cause the server to crash.
  • CVE-2016-5424: database and role names with embedded special characters can allow code injection during administrative operations like pg_dumpall.
  • The fix for the second issue also adds an option, -reuse-previous, to psql's connect command. pg_dumpall will also refuse to handle database and role names containing line breaks after the update. For more information on these issues and how they affect backwards-compatibility, see the Release Notes.
  • 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 9.5, but many affect all supported versions:
  • Fix misbehaviors of IS NULL/IS NOT NULL with composite values
  • Fix three areas where INSERT ... ON CONFLICT failed to work properly with other SQL features.
  • Make INET and CIDR data types properly reject bad IPv6 values
  • Prevent crash in "point ## lseg" operator for NaN input
  • Avoid possible crash in pg_get_expr()
  • Fix several one-byte buffer over-reads in to_number()
  • Don't needlessly plan query if WITH NO DATA is specified
  • Avoid crash-unsafe state in expensive heap_update() paths
  • Fix hint bit update during WAL replay of row locking operations
  • Avoid unnecessary "could not serialize access" with FOR KEY SHARE
  • Avoid crash in postgres -C when the specified variable is a null string
  • Fix two issues with logical decoding and subtransactions
  • Ensure that backends see up-to-date statistics for shared catalogs
  • Prevent possible failure when vacuuming multixact IDs in an upgraded database
  • When a manual ANALYZE specifies columns, don't reset changes_since_analyze
  • Fix ANALYZE's overestimation of n_distinct for columns with nulls
  • Fix bug in b-tree mark/restore processing
  • Fix building of large (bigger than shared_buffers) hash indexes
  • Prevent infinite loop in GiST index build with NaN values
  • Fix possible crash during a nearest-neighbor indexscan
  • Fix "PANIC: failed to add BRIN tuple" error
  • Prevent possible crash during background worker shutdown
  • Many fixes for issues in parallel pg_dump and pg_restore
  • Make pg_basebackup accept -Z 0 as no compression
  • Make regression tests safe for Danish and Welsh locales
  • The libpq client library has also been updated to support future two-part PostgreSQL version numbers. This update also contains tzdata release 2016f, with updates for Kemerovo, Novosibirsk, Azerbaijan, Belarus, and Morocco.
  • EOL Warning for Version 9.1:
  • PostgreSQL version 9.1 will be End-of-Life in September 2016. The project expects to only release one more update for that version. We urge users to start planning an upgrade to a later version of PostgreSQL as soon as possible. See our Versioning Policy for more information.
  • Updating:
  • All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries. Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.

New in Postgres.app 9.5.1.0 (Feb 11, 2016)

  • POSTGRES.APP CHANGES:
  • PostGIS 2.2.1
  • OpenSSL 1.0.1r
  • POSTGRESQL CHANGES:
  • Security Fixes for Regular Expressions, PL/Java:
  • This release closes security hole CVE-2016-0773, an issue with regular expression (regex) parsing. Prior code allowed users to pass in expressions which included out-of-range Unicode characters, triggering a backend crash. This issue is critical for PostgreSQL systems with untrusted users or which generate regexes based on user input.
  • The update also fixes CVE-2016-0766, a privilege escalation issue for users of PL/Java. Certain custom configuration settings (GUCS) for PL/Java will now be modifiable only by the database superuser.
  • Other Fixes and Improvements:
  • In addition to the above, many other issues were patched in this release based on bugs reported by our users over the last few months. This includes multiple fixes for new features introduced in version 9.5.0, as well as refactoring of pg_dump to eliminate a number of chronic issues with backing up EXTENSIONs.
  • Among them are:
  • Fix many issues in pg_dump with specific object types
  • Prevent over-eager pushdown of HAVING clauses for GROUPING SETS
  • Fix deparsing error with ON CONFLICT ... WHERE clauses
  • Fix tableoid errors for postgres_fdw
  • Prevent floating-point exceptions in pgbench
  • Make \det search Foreign Table names consistently
  • Fix quoting of domain constraint names in pg_dump
  • Prevent putting expanded objects into Const nodes
  • Allow compile of PL/Java on Windows
  • Fix "unresolved symbol" errors in PL/Python execution
  • Allow Python2 and Python3 to be used in the same database
  • Add support for Python 3.5 in PL/Python
  • Fix issue with subdirectory creation during initdb
  • Make pg_ctl report status correctly on Windows
  • Suppress confusing error when using pg_receivexlog with older servers
  • Multiple documentation corrections and additions
  • Fix erroneous hash calculations in gin_extract_jsonb_path()
  • This update also contains tzdata release 2016a, with updates for Cayman Islands, Metlakatla, Trans-Baikal Territory (Zabaykalsky Krai), and Pakistan.

New in Postgres.app 9.5.0.0 (Jan 7, 2016)

  • PostgreSQL 9.5.0
  • PostGIS 2.2.1
  • OpenSSL 1.0.1q

New in Postgres.app 9.5 Beta 2.0 (Nov 12, 2015)

  • OpenSSL 1.0.1p
  • PostGIS 2.2.0

New in Postgres.app 9.5 Beta 1.0 (Oct 9, 2015)

  • Many bugs and issues reported by our users and contributors have been fixed since the release of Alpha2. These include:
  • significant adjustments to Row Level Security (RLS) semantics
  • deadlock with LWLock improvements
  • index corruption issue with BRIN indexes
  • couldn't connect using PGSSLMODE=require on Windows
  • various problems with commit timestamp tracking
  • hash join memory leak
  • inconsistent behavior of jsonb_set with array append

New in Postgres.app 9.4.5.0 (Oct 8, 2015)

  • Changes:
  • Guard against stack overflows in json parsing (Oskari Saarenmaa)
  • If an application constructs PostgreSQL json or jsonb values from arbitrary user input, the application's users can reliably crash the PostgreSQL server, causing momentary denial of service. (CVE-2015-5289)
  • Fix contrib/pgcrypto to detect and report too-short crypt() salts (Josh Kupershmidt)
  • Certain invalid salt arguments crashed the server or disclosed a few bytes of server memory. We have not ruled out the viability of attacks that arrange for presence of confidential information in the disclosed bytes, but they seem unlikely. (CVE-2015-5288)
  • Fix subtransaction cleanup after a portal (cursor) belonging to an outer subtransaction fails (Tom Lane, Michael Paquier)
  • A function executed in an outer-subtransaction cursor could cause an assertion failure or crash by referencing a relation created within an inner subtransaction.
  • Fix possible deadlock during WAL insertion when commit_delay is set (Heikki Linnakangas)
  • Ensure all relations referred to by an updatable view are properly locked during an update statement (Dean Rasheed)
  • Fix insertion of relations into the relation cache "init file" (Tom Lane)
  • An oversight in a patch in the most recent minor releases caused pg_trigger_tgrelid_tgname_index to be omitted from the init file. Subsequent sessions detected this, then deemed the init file to be broken and silently ignored it, resulting in a significant degradation in session startup time. In addition to fixing the bug, install some guards so that any similar future mistake will be more obvious.
  • Avoid O(N^2) behavior when inserting many tuples into a SPI query result (Neil Conway)
  • Improve LISTEN startup time when there are many unread notifications (Matt Newell)
  • Fix performance problem when a session alters large numbers of foreign key constraints (Jan Wieck, Tom Lane)
  • This was seen primarily when restoring pg_dump output for databases with many thousands of tables.
  • Disable SSL renegotiation by default (Michael Paquier, Andres Freund)
  • While use of SSL renegotiation is a good idea in theory, we have seen too many bugs in practice, both in the underlying OpenSSL library and in our usage of it. Renegotiation will be removed entirely in 9.5 and later. In the older branches, just change the default value of ssl_renegotiation_limit to zero (disabled).
  • Lower the minimum values of the *_freeze_max_age parameters (Andres Freund)
  • This is mainly to make tests of related behavior less time-consuming, but it may also be of value for installations with limited disk space.
  • Limit the maximum value of wal_buffers to 2GB to avoid server crashes (Josh Berkus)
  • Avoid logging complaints when a parameter that can only be set at server start appears multiple times in postgresql.conf, and fix counting of line numbers after an include_dir directive (Tom Lane)
  • Fix rare internal overflow in multiplication of numeric values (Dean Rasheed)
  • Guard against hard-to-reach stack overflows involving record types, range types, json, jsonb, tsquery, ltxtquery and query_int (Noah Misch)
  • Fix handling of DOW and DOY in datetime input (Greg Stark)
  • These tokens aren't meant to be used in datetime values, but previously they resulted in opaque internal error messages rather than "invalid input syntax".
  • Add more query-cancel checks to regular expression matching (Tom Lane)
  • Add recursion depth protections to regular expression, SIMILAR TO, and LIKE matching (Tom Lane)
  • Suitable search patterns and a low stack depth limit could lead to stack-overrun crashes.
  • Fix potential infinite loop in regular expression execution (Tom Lane)
  • A search pattern that can apparently match a zero-length string, but actually doesn't match because of a back reference, could lead to an infinite loop.
  • In regular expression execution, correctly record match data for capturing parentheses within a quantifier even when the match is zero-length (Tom Lane)
  • Fix low-memory failures in regular expression compilation (Andreas Seltenreich)
  • Fix low-probability memory leak during regular expression execution (Tom Lane)
  • Fix rare low-memory failure in lock cleanup during transaction abort (Tom Lane)
  • Fix "unexpected out-of-memory situation during sort" errors when using tuplestores with small work_mem settings (Tom Lane)
  • Fix very-low-probability stack overrun in qsort (Tom Lane)
  • Fix "invalid memory alloc request size" failure in hash joins with large work_mem settings (Tomas Vondra, Tom Lane)
  • Fix assorted planner bugs (Tom Lane)
  • These mistakes could lead to incorrect query plans that would give wrong answers, or to assertion failures in assert-enabled builds, or to odd planner errors such as "could not devise a query plan for the given query", "could not find pathkey item to sort", "plan should not reference subplan's variable", or "failed to assign all NestLoopParams to plan nodes". Thanks are due to Andreas Seltenreich and Piotr Stefaniak for fuzz testing that exposed these problems.
  • Improve planner's performance for UPDATE/DELETE on large inheritance sets (Tom Lane, Dean Rasheed)
  • Ensure standby promotion trigger files are removed at postmaster startup (Michael Paquier, Fujii Masao)
  • This prevents unwanted promotion from occurring if these files appear in a database backup that is used to initialize a new standby server.
  • During postmaster shutdown, ensure that per-socket lock files are removed and listen sockets are closed before we remove the postmaster.pid file (Tom Lane)
  • This avoids race-condition failures if an external script attempts to start a new postmaster as soon as pg_ctl stop returns.
  • Ensure that the postmaster does not exit until all its child processes are gone, even in an immediate shutdown (Tom Lane)
  • Like the previous item, this avoids possible race conditions against a subsequently-started postmaster.
  • Fix postmaster's handling of a startup-process crash during crash recovery (Tom Lane)
  • If, during a crash recovery cycle, the startup process crashes without having restored database consistency, we'd try to launch a new startup process, which typically would just crash again, leading to an infinite loop.
  • Make emergency autovacuuming for multixact wraparound more robust (Andres Freund)
  • Do not print a WARNING when an autovacuum worker is already gone when we attempt to signal it, and reduce log verbosity for such signals (Tom Lane)
  • Prevent autovacuum launcher from sleeping unduly long if the server clock is moved backwards a large amount (Álvaro Herrera)
  • Ensure that cleanup of a GIN index's pending-insertions list is interruptable by cancel requests (Jeff Janes)
  • Allow all-zeroes pages in GIN indexes to be reused (Heikki Linnakangas)
  • Such a page might be left behind after a crash.
  • Fix handling of all-zeroes pages in SP-GiST indexes (Heikki Linnakangas)
  • VACUUM attempted to recycle such pages, but did so in a way that wasn't crash-safe.
  • Fix off-by-one error that led to otherwise-harmless warnings about "apparent wraparound" in subtrans/multixact truncation (Thomas Munro)
  • Fix misreporting of CONTINUE and MOVE statement types in PL/pgSQL's error context messages (Pavel Stehule, Tom Lane)
  • Fix PL/Perl to handle non-ASCII error message texts correctly (Alex Hunsaker)
  • Fix PL/Python crash when returning the string representation of a record result (Tom Lane)
  • Fix some places in PL/Tcl that neglected to check for failure of malloc() calls (Michael Paquier, Álvaro Herrera)
  • In contrib/isn, fix output of ISBN-13 numbers that begin with 979 (Fabien Coelho)
  • EANs beginning with 979 (but not 9790) are considered ISBNs, but they must be printed in the new 13-digit format, not the 10-digit format.
  • Improve contrib/pg_stat_statements' handling of query-text garbage collection (Peter Geoghegan)
  • The external file containing query texts could bloat to very large sizes; once it got past 1GB attempts to trim it would fail, soon leading to situations where the file could not be read at all.
  • Improve contrib/postgres_fdw's handling of collation-related decisions (Tom Lane)
  • The main user-visible effect is expected to be that comparisons involving varchar columns will be sent to the remote server for execution in more cases than before.
  • Improve libpq's handling of out-of-memory conditions (Michael Paquier, Heikki Linnakangas)
  • Fix memory leaks and missing out-of-memory checks in ecpg (Michael Paquier)
  • Fix psql's code for locale-aware formatting of numeric output (Tom Lane)
  • The formatting code invoked by \pset numericlocale on did the wrong thing for some uncommon cases such as numbers with an exponent but no decimal point. It could also mangle already-localized output from the money data type.
  • Prevent crash in psql's \c command when there is no current connection (Noah Misch)
  • Make pg_dump handle inherited NOT VALID check constraints correctly (Tom Lane)
  • Fix selection of default zlib compression level in pg_dump's directory output format (Andrew Dunstan)
  • Ensure that temporary files created during a pg_dump run with tar-format output are not world-readable (Michael Paquier)
  • Fix pg_dump and pg_upgrade to support cases where the postgres or template1 database is in a non-default tablespace (Marti Raudsepp, Bruce Momjian)
  • Fix pg_dump to handle object privileges sanely when dumping from a server too old to have a particular privilege type (Tom Lane)
  • When dumping data types from pre-9.2 servers, and when dumping functions or procedural languages from pre-7.3 servers, pg_dump would produce GRANT/REVOKE commands that revoked the owner's grantable privileges and instead granted all privileges to PUBLIC. Since the privileges involved are just USAGE and EXECUTE, this isn't a security problem, but it's certainly a surprising representation of the older systems' behavior. Fix it to leave the default privilege state alone in these cases.
  • Fix pg_dump to dump shell types (Tom Lane)
  • Shell types (that is, not-yet-fully-defined types) aren't useful for much, but nonetheless pg_dump should dump them.
  • Fix assorted minor memory leaks in pg_dump and other client-side programs (Michael Paquier)
  • Fix pgbench's progress-report behavior when a query, or pgbench itself, gets stuck (Fabien Coelho)
  • Fix spinlock assembly code for Alpha hardware (Tom Lane)
  • Fix spinlock assembly code for PPC hardware to be compatible with AIX's native assembler (Tom Lane)
  • Building with gcc didn't work if gcc had been configured to use the native assembler, which is becoming more common.
  • On AIX, test the -qlonglong compiler option rather than just assuming it's safe to use (Noah Misch)
  • On AIX, use -Wl,-brtllib link option to allow symbols to be resolved at runtime (Noah Misch)
  • Perl relies on this ability in 5.8.0 and later.
  • Avoid use of inline functions when compiling with 32-bit xlc, due to compiler bugs (Noah Misch)
  • Use librt for sched_yield() when necessary, which it is on some Solaris versions (Oskari Saarenmaa)
  • Translate encoding UHC as Windows code page 949 (Noah Misch)
  • This fixes presentation of non-ASCII log messages from processes that are not attached to any particular database, such as the postmaster.
  • On Windows, avoid failure when doing encoding conversion to UTF16 outside a transaction, such as for log messages (Noah Misch)
  • Fix postmaster startup failure due to not copying setlocale()'s return value (Noah Misch)
  • This has been reported on Windows systems with the ANSI code page set to CP936 ("Chinese (Simplified, PRC)"), and may occur with other multibyte code pages.
  • Fix Windows install.bat script to handle target directory names that contain spaces (Heikki Linnakangas)
  • Make the numeric form of the PostgreSQL version number (e.g., 90405) readily available to extension Makefiles, as a variable named VERSION_NUM (Michael Paquier)
  • Update time zone data files to tzdata release 2015g for DST law changes in Cayman Islands, Fiji, Moldova, Morocco, Norfolk Island, North Korea, Turkey, and Uruguay. There is a new zone name America/Fort_Nelson for the Canadian Northern Rockies.

New in Postgres.app 9.4.4.1 (Jul 20, 2015)

  • Updated OpenSSL to 1.0.1p

New in Postgres.app 9.5 Alpha 1.0 (Jul 3, 2015)

  • The first preview of this years Postgres release, including the newest PostGIS preview.
  • PostgreSQL 9.5alpha1
  • PostGIS 2.2.0dev
  • Make sure to update your PATH after installing this app.

New in Postgres.app 9.4.4.0 (Jun 16, 2015)

  • PostgreSQL 9.4.4
  • OpenSSL 1.0.1o

New in Postgres.app 9.4.2.0 (May 23, 2015)

  • PostgreSQL 9.4.2
  • PostGIS 2.1.7
  • GDAL 1.11.2
  • GEOS 3.4.2
  • OpenSSL 1.0.1m
  • Proj4 4.9.1
  • v8 3.18

New in Postgres.app 9.4.1.2 (Apr 30, 2015)

  • GDAL now statically linked to Proj4 (might fix #239 and #243)
  • includes fix for light menu bar icon #258
  • updated PostGIS to version 2.1.7
  • updated GDAL to 1.11.2
  • updated libxml2 to 2.9.2
  • updated proj4 to 4.9.1

New in Postgres.app 9.4.1.0 (Feb 7, 2015)

  • PostgreSQL 9.4.1
  • OpenSSL 1.0.1l
  • PostGIS 2.1.5

New in Postgres.app 9.4.0.1 (Dec 29, 2014)

  • Fix bug with plv8 (issue #240)
  • Fix problem with initdb when language/region settings in system preferences don't match (issue #237)

New in Postgres.app 9.4.0.0 (Dec 27, 2014)

  • Note: unlike the release candidate, this version is built without the ICU patch to ensure compatibility with other PostgreSQL installations.