PostgreSQL 9.4.26 (64-bit)

What's new in this version:

- Avoid failure in logical decoding when a large transaction must be spilled into many separate temporary files
- Fix failure in logical replication publisher after a database crash and restart
- Avoid memory leak when there are no free dynamic shared memory slots
- Ignore the CONCURRENTLY option when performing an index creation, drop, or rebuild on a temporary table
- This avoids strange failures if the temporary table has an ON COMMIT action. There is no benefit in using CONCURRENTLY for a temporary table anyway, since other sessions cannot access the table, making the extra processing pointless.
- Fix possible failure when resetting expression indexes on temporary tables that are marked ON COMMIT DELETE ROWS
- Fix handling of deleted pages in GIN indexes
- Avoid possible deadlocks, incorrect updates of a deleted page's state, and failure to traverse through a recently-deleted page
- Fix possible crash with a SubPlan (sub-SELECT) within a multi-row VALUES list
- Fix unlikely crash with pass-by-reference aggregate transition states
- Improve error reporting in to_date() and to_timestamp()
- Reports about incorrect month or day names in input strings could truncate the input in the middle of a multi-byte character, leading to an improperly encoded error message that could cause follow-on failures. Truncate at the next whitespace instead.
- Fix off-by-one result for EXTRACT(ISOYEAR FROM timestamp) for BC dates
- Avoid stack overflow in information_schema views when a self-referential view exists in the system catalogs
- A self-referential view can't work; it will always result in infinite recursion. We handled that situation correctly when trying to execute the view, but not when inquiring whether it is automatically updatable.
- Improve performance of hash joins with very large inner relations
- Fix edge-case crashes and misestimations in selectivity calculations for the <@ and @> range operators
- Improve error reporting for attempts to use automatic updating of views with conditional INSTEAD rules
- This has never been supported, but previously the error was thrown only at execution time, so that it could be masked by planner errors
- Prevent a composite type from being included in itself indirectly via a range type
- Fix error reporting for index expressions of prohibited types
- Fix dumping of views that contain only a VALUES list to handle cases where a view output column has been renamed
- Allow libpq to parse all GSS-related connection parameters even when the GSSAPI code hasn't been compiled in
- This makes the behavior similar to our SSL support, where it was long ago deemed to be a good idea to always accept all the related parameters, even if some are ignored or restricted due to lack of the feature in a particular build
- Fix incorrect handling of %b and %B format codes in ecpg's PGTYPEStimestamp_fmt_asc() function
- Due to an off-by-one error, these codes would print the wrong month name, or possibly crash.
- Fix parallel pg_dump/pg_restore to more gracefully handle failure to create worker processes
- Prevent possible crash or lockup when attempting to terminate a parallel pg_dump/pg_restore run via a signal
- In pg_upgrade, look inside arrays and ranges while searching for non-upgradable data types in tables
- Apply more thorough syntax checking to createuser's --connection-limit option
- In contrib/dict_int, reject maxlen settings less than one
- This prevents a possible crash with silly settings for that parameter
- Disallow NULL category values in contrib/tablefunc's crosstab() function
- This case never worked usefully, and it would crash on some platforms
- Mark some timeout and statistics-tracking GUC variables as PGDLLIMPORT, to allow extensions to access them on Windows
- This applies to idle_in_transaction_session_timeout, lock_timeout, statement_timeout, track_activities, track_counts, and track_functions.
- Fix race condition that led to delayed delivery of interprocess signals on Windows
- This caused visible timing oddities in NOTIFY, and perhaps other misbehavior
- On Windows, retry a few times after an ERROR_ACCESS_DENIED file access failure
- This helps cope with cases where a file open attempt fails because the targeted file is flagged for deletion but not yet actually gone. pg_ctl, for example, frequently failed with such an error when probing to see if the postmaster had shut down yet.