PostgreSQL 9.1.19 release changes

• Same change PostgreSQL 9.4.5 · Fix contrib/pgcrypto to detect and report too-short crypt() salts
• Same change PostgreSQL 9.3.10 · Fix contrib/pgcrypto to detect and report too-short crypt() salts
• Same change PostgreSQL 9.2.14 · Fix contrib/pgcrypto to detect and report too-short crypt() salts
• Same change PostgreSQL 9.0.23 · Fix contrib/pgcrypto to detect and report too-short crypt() salts

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix subtransaction cleanup after a portal (cursor) belonging to an outer subtransaction fails
• Same change PostgreSQL 9.3.10 · Fix subtransaction cleanup after a portal (cursor) belonging to an outer subtransaction fails
• Same change PostgreSQL 9.2.14 · Fix subtransaction cleanup after a portal (cursor) belonging to an outer subtransaction fails
• Same change PostgreSQL 9.0.23 · Fix subtransaction cleanup after a portal (cursor) belonging to an outer subtransaction fails

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix insertion of relations into the relation cache "init file"
• Same change PostgreSQL 9.3.10 · Fix insertion of relations into the relation cache "init file"
• Same change PostgreSQL 9.2.14 · Fix insertion of relations into the relation cache "init file"
• Same change PostgreSQL 9.0.23 · Fix insertion of relations into the relation cache "init file"

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Avoid O(N^2) behavior when inserting many tuples into a SPI query result
• Same change PostgreSQL 9.3.10 · Avoid O(N^2) behavior when inserting many tuples into a SPI query result
• Same change PostgreSQL 9.2.14 · Avoid O(N^2) behavior when inserting many tuples into a SPI query result
• Same change PostgreSQL 9.0.23 · Avoid O(N^2) behavior when inserting many tuples into a SPI query result

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Improve LISTEN startup time when there are many unread notifications
• Same change PostgreSQL 9.3.10 · Improve LISTEN startup time when there are many unread notifications
• Same change PostgreSQL 9.2.14 · Improve LISTEN startup time when there are many unread notifications
• Same change PostgreSQL 9.0.23 · Improve LISTEN startup time when there are many unread notifications

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.2.14 · Back-patch 9.3-era addition of per-resource-owner lock caches

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Disable SSL renegotiation by default
• Same change PostgreSQL 9.3.10 · Disable SSL renegotiation by default
• Same change PostgreSQL 9.2.14 · Disable SSL renegotiation by default
• Same change PostgreSQL 9.0.23 · Disable SSL renegotiation by default

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Lower the minimum values of the *_freeze_max_age parameters
• Same change PostgreSQL 9.3.10 · Lower the minimum values of the *_freeze_max_age parameters
• Same change PostgreSQL 9.2.14 · Lower the minimum values of the *_freeze_max_age parameters
• Same change PostgreSQL 9.0.23 · Lower the minimum values of the *_freeze_max_age parameters

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Limit the maximum value of wal_buffers to 2GB to avoid server crashes
• Same change PostgreSQL 9.3.10 · Limit the maximum value of wal_buffers to 2GB to avoid server crashes
• Same change PostgreSQL 9.2.14 · Limit the maximum value of wal_buffers to 2GB to avoid server crashes
• Same change PostgreSQL 9.0.23 · Limit the maximum value of wal_buffers to 2GB to avoid server crashes

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix rare internal overflow in multiplication of numeric values
• Same change PostgreSQL 9.3.10 · Fix rare internal overflow in multiplication of numeric values
• Same change PostgreSQL 9.2.14 · Fix rare internal overflow in multiplication of numeric values
• Same change PostgreSQL 9.0.23 · Fix rare internal overflow in multiplication of numeric values

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Guard against hard-to-reach stack overflows involving record types, range types, json, jsonb, tsquery, ltxtquery and query_int
• Same change PostgreSQL 9.3.10 · Guard against hard-to-reach stack overflows involving record types, range types, json, jsonb, tsquery, ltxtquery and query_int
• Same change PostgreSQL 9.2.14 · Guard against hard-to-reach stack overflows involving record types, range types, json, jsonb, tsquery, ltxtquery and query_int
• Same change PostgreSQL 9.0.23 · Guard against hard-to-reach stack overflows involving record types, range types, json, jsonb, tsquery, ltxtquery and query_int

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix handling of DOW and DOY in datetime input
• Same change PostgreSQL 9.3.10 · Fix handling of DOW and DOY in datetime input
• Same change PostgreSQL 9.2.14 · Fix handling of DOW and DOY in datetime input
• Same change PostgreSQL 9.0.23 · Fix handling of DOW and DOY in datetime input

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Add more query-cancel checks to regular expression matching
• Same change PostgreSQL 9.3.10 · Add more query-cancel checks to regular expression matching
• Same change PostgreSQL 9.2.14 · Add more query-cancel checks to regular expression matching
• Same change PostgreSQL 9.0.23 · Add more query-cancel checks to regular expression matching

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Add recursion depth protections to regular expression, SIMILAR TO, and LIKE matching
• Same change PostgreSQL 9.3.10 · Add recursion depth protections to regular expression, SIMILAR TO, and LIKE matching
• Same change PostgreSQL 9.2.14 · Add recursion depth protections to regular expression, SIMILAR TO, and LIKE matching
• Same change PostgreSQL 9.0.23 · Add recursion depth protections to regular expression, SIMILAR TO, and LIKE matching

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix potential infinite loop in regular expression execution
• Same change PostgreSQL 9.3.10 · Fix potential infinite loop in regular expression execution
• Same change PostgreSQL 9.2.14 · Fix potential infinite loop in regular expression execution
• Same change PostgreSQL 9.0.23 · Fix potential infinite loop in regular expression execution

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix low-memory failures in regular expression compilation
• Same change PostgreSQL 9.3.10 · Fix low-memory failures in regular expression compilation
• Same change PostgreSQL 9.2.14 · Fix low-memory failures in regular expression compilation
• Same change PostgreSQL 9.0.23 · Fix low-memory failures in regular expression compilation

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix low-probability memory leak during regular expression execution
• Same change PostgreSQL 9.3.10 · Fix low-probability memory leak during regular expression execution
• Same change PostgreSQL 9.2.14 · Fix low-probability memory leak during regular expression execution
• Same change PostgreSQL 9.0.23 · Fix low-probability memory leak during regular expression execution

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix rare low-memory failure in lock cleanup during transaction abort
• Same change PostgreSQL 9.3.10 · Fix rare low-memory failure in lock cleanup during transaction abort
• Same change PostgreSQL 9.2.14 · Fix rare low-memory failure in lock cleanup during transaction abort
• Same change PostgreSQL 9.0.23 · Fix rare low-memory failure in lock cleanup during transaction abort

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix "unexpected out-of-memory situation during sort" errors when using tuplestores with small work_mem settings
• Same change PostgreSQL 9.3.10 · Fix "unexpected out-of-memory situation during sort" errors when using tuplestores with small work_mem settings
• Same change PostgreSQL 9.2.14 · Fix "unexpected out-of-memory situation during sort" errors when using tuplestores with small work_mem settings
• Same change PostgreSQL 9.0.23 · Fix "unexpected out-of-memory situation during sort" errors when using tuplestores with small work_mem settings

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix very-low-probability stack overrun in qsort
• Same change PostgreSQL 9.3.10 · Fix very-low-probability stack overrun in qsort
• Same change PostgreSQL 9.2.14 · Fix very-low-probability stack overrun in qsort
• Same change PostgreSQL 9.0.23 · Fix very-low-probability stack overrun in qsort

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix "invalid memory alloc request size" failure in hash joins with large work_mem settings
• Same change PostgreSQL 9.3.10 · Fix "invalid memory alloc request size" failure in hash joins with large work_mem settings
• Same change PostgreSQL 9.2.14 · Fix "invalid memory alloc request size" failure in hash joins with large work_mem settings
• Same change PostgreSQL 9.0.23 · Fix "invalid memory alloc request size" failure in hash joins with large work_mem settings

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix assorted planner bugs
• Same change PostgreSQL 9.3.10 · Fix assorted planner bugs
• Same change PostgreSQL 9.2.14 · Fix assorted planner bugs
• Same change PostgreSQL 9.0.23 · Fix assorted planner bugs

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.0.23 · Use fuzzy path cost tiebreaking rule in all supported branches

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Ensure standby promotion trigger files are removed at postmaster startup
• Same change PostgreSQL 9.3.10 · Ensure standby promotion trigger files are removed at postmaster startup
• Same change PostgreSQL 9.2.14 · Ensure standby promotion trigger files are removed at postmaster startup

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · During postmaster shutdown, ensure that per-socket lock files are removed and listen sockets are closed before we remove the postmaster.pid file
• Same change PostgreSQL 9.3.10 · During postmaster shutdown, ensure that per-socket lock files are removed and listen sockets are closed before we remove the postmaster.pid file
• Same change PostgreSQL 9.2.14 · During postmaster shutdown, ensure that per-socket lock files are removed and listen sockets are closed before we remove the postmaster.pid file
• Same change PostgreSQL 9.0.23 · During postmaster shutdown, ensure that per-socket lock files are removed and listen sockets are closed before we remove the postmaster.pid file

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix postmaster's handling of a startup-process crash during crash recovery
• Same change PostgreSQL 9.3.10 · Fix postmaster's handling of a startup-process crash during crash recovery
• Same change PostgreSQL 9.2.14 · Fix postmaster's handling of a startup-process crash during crash recovery
• Same change PostgreSQL 9.0.23 · Fix postmaster's handling of a startup-process crash during crash recovery

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · 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
• Same change PostgreSQL 9.3.10 · 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
• Same change PostgreSQL 9.2.14 · 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
• Same change PostgreSQL 9.0.23 · 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

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Prevent autovacuum launcher from sleeping unduly long if the server clock is moved backwards a large amount
• Same change PostgreSQL 9.3.10 · Prevent autovacuum launcher from sleeping unduly long if the server clock is moved backwards a large amount
• Same change PostgreSQL 9.2.14 · Prevent autovacuum launcher from sleeping unduly long if the server clock is moved backwards a large amount
• Same change PostgreSQL 9.0.23 · Prevent autovacuum launcher from sleeping unduly long if the server clock is moved backwards a large amount

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Ensure that cleanup of a GIN index's pending-insertions list is interruptable by cancel requests
• Same change PostgreSQL 9.3.10 · Ensure that cleanup of a GIN index's pending-insertions list is interruptable by cancel requests
• Same change PostgreSQL 9.2.14 · Ensure that cleanup of a GIN index's pending-insertions list is interruptable by cancel requests
• Same change PostgreSQL 9.0.23 · Ensure that cleanup of a GIN index's pending-insertions list is interruptable by cancel requests

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Allow all-zeroes pages in GIN indexes to be reused
• Same change PostgreSQL 9.3.10 · Allow all-zeroes pages in GIN indexes to be reused
• Same change PostgreSQL 9.2.14 · Allow all-zeroes pages in GIN indexes to be reused
• Same change PostgreSQL 9.0.23 · Allow all-zeroes pages in GIN indexes to be reused

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix off-by-one error that led to otherwise-harmless warnings about "apparent wraparound" in subtrans/multixact truncation
• Same change PostgreSQL 9.3.10 · Fix off-by-one error that led to otherwise-harmless warnings about "apparent wraparound" in subtrans/multixact truncation
• Same change PostgreSQL 9.2.14 · Fix off-by-one error that led to otherwise-harmless warnings about "apparent wraparound" in subtrans/multixact truncation
• Same change PostgreSQL 9.0.23 · Fix off-by-one error that led to otherwise-harmless warnings about "apparent wraparound" in subtrans/multixact truncation

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix misreporting of CONTINUE and MOVE statement types in PL/pgSQL's error context messages
• Same change PostgreSQL 9.3.10 · Fix misreporting of CONTINUE and MOVE statement types in PL/pgSQL's error context messages
• Same change PostgreSQL 9.2.14 · Fix misreporting of CONTINUE and MOVE statement types in PL/pgSQL's error context messages
• Same change PostgreSQL 9.0.23 · Fix misreporting of CONTINUE and MOVE statement types in PL/pgSQL's error context messages

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix PL/Perl to handle non-ASCII error message texts correctly
• Same change PostgreSQL 9.3.10 · Fix PL/Perl to handle non-ASCII error message texts correctly
• Same change PostgreSQL 9.2.14 · Fix PL/Perl to handle non-ASCII error message texts correctly

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix PL/Python crash when returning the string representation of a record result
• Same change PostgreSQL 9.3.10 · Fix PL/Python crash when returning the string representation of a record result
• Same change PostgreSQL 9.2.14 · Fix PL/Python crash when returning the string representation of a record result

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix some places in PL/Tcl that neglected to check for failure of malloc() calls
• Same change PostgreSQL 9.3.10 · Fix some places in PL/Tcl that neglected to check for failure of malloc() calls
• Same change PostgreSQL 9.2.14 · Fix some places in PL/Tcl that neglected to check for failure of malloc() calls
• Same change PostgreSQL 9.0.23 · Fix some places in PL/Tcl that neglected to check for failure of malloc() calls

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · In contrib/isn, fix output of ISBN-13 numbers that begin with 979
• Same change PostgreSQL 9.3.10 · In contrib/isn, fix output of ISBN-13 numbers that begin with 979
• Same change PostgreSQL 9.2.14 · In contrib/isn, fix output of ISBN-13 numbers that begin with 979

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Improve libpq's handling of out-of-memory conditions
• Same change PostgreSQL 9.3.10 · Improve libpq's handling of out-of-memory conditions
• Same change PostgreSQL 9.2.14 · Improve libpq's handling of out-of-memory conditions
• Same change PostgreSQL 9.0.23 · Improve libpq's handling of out-of-memory conditions

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix memory leaks and missing out-of-memory checks in ecpg
• Same change PostgreSQL 9.3.10 · Fix memory leaks and missing out-of-memory checks in ecpg
• Same change PostgreSQL 9.2.14 · Fix memory leaks and missing out-of-memory checks in ecpg
• Same change PostgreSQL 9.0.23 · Fix memory leaks and missing out-of-memory checks in ecpg

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix psql's code for locale-aware formatting of numeric output
• Same change PostgreSQL 9.3.10 · Fix psql's code for locale-aware formatting of numeric output
• Same change PostgreSQL 9.2.14 · Fix psql's code for locale-aware formatting of numeric output
• Same change PostgreSQL 9.0.23 · Fix psql's code for locale-aware formatting of numeric output

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Prevent crash in psql's \c command when there is no current connection
• Same change PostgreSQL 9.3.10 · Prevent crash in psql's \c command when there is no current connection
• Same change PostgreSQL 9.2.14 · Prevent crash in psql's \c command when there is no current connection
• Same change PostgreSQL 9.0.23 · Prevent crash in psql's \c command when there is no current connection

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix selection of default zlib compression level in pg_dump's directory output format
• Same change PostgreSQL 9.3.10 · Fix selection of default zlib compression level in pg_dump's directory output format
• Same change PostgreSQL 9.2.14 · Fix selection of default zlib compression level in pg_dump's directory output format

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Ensure that temporary files created during a pg_dump run with tar-format output are not world-readable
• Same change PostgreSQL 9.3.10 · Ensure that temporary files created during a pg_dump run with tar-format output are not world-readable
• Same change PostgreSQL 9.2.14 · Ensure that temporary files created during a pg_dump run with tar-format output are not world-readable
• Same change PostgreSQL 9.0.23 · Ensure that temporary files created during a pg_dump run with tar-format output are not world-readable

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix pg_dump and pg_upgrade to support cases where the postgres or template1 database is in a non-default tablespace
• Same change PostgreSQL 9.3.10 · Fix pg_dump and pg_upgrade to support cases where the postgres or template1 database is in a non-default tablespace
• Same change PostgreSQL 9.2.14 · Fix pg_dump and pg_upgrade to support cases where the postgres or template1 database is in a non-default tablespace
• Same change PostgreSQL 9.0.23 · Fix pg_dump and pg_upgrade to support cases where the postgres or template1 database is in a non-default tablespace

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.0.23 · Fix pg_dump to handle object privileges sanely when dumping from a server too old to have a particular privilege type

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix pg_dump to dump shell types
• Same change PostgreSQL 9.3.10 · Fix pg_dump to dump shell types
• Same change PostgreSQL 9.2.14 · Fix pg_dump to dump shell types
• Same change PostgreSQL 9.0.23 · Fix pg_dump to dump shell types

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix assorted minor memory leaks in pg_dump and other client-side programs
• Same change PostgreSQL 9.3.10 · Fix assorted minor memory leaks in pg_dump and other client-side programs
• Same change PostgreSQL 9.2.14 · Fix assorted minor memory leaks in pg_dump and other client-side programs

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix spinlock assembly code for PPC hardware to be compatible with AIX's native assembler
• Same change PostgreSQL 9.3.10 · Fix spinlock assembly code for PPC hardware to be compatible with AIX's native assembler
• Same change PostgreSQL 9.2.14 · Fix spinlock assembly code for PPC hardware to be compatible with AIX's native assembler
• Same change PostgreSQL 9.0.23 · Fix spinlock assembly code for PPC hardware to be compatible with AIX's native assembler

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · On AIX, test the -qlonglong compiler option rather than just assuming it's safe to use
• Same change PostgreSQL 9.3.10 · On AIX, test the -qlonglong compiler option rather than just assuming it's safe to use
• Same change PostgreSQL 9.2.14 · On AIX, test the -qlonglong compiler option rather than just assuming it's safe to use
• Same change PostgreSQL 9.0.23 · On AIX, test the -qlonglong compiler option rather than just assuming it's safe to use

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · On AIX, use -Wl,-brtllib link option to allow symbols to be resolved at runtime
• Same change PostgreSQL 9.3.10 · On AIX, use -Wl,-brtllib link option to allow symbols to be resolved at runtime
• Same change PostgreSQL 9.2.14 · On AIX, use -Wl,-brtllib link option to allow symbols to be resolved at runtime
• Same change PostgreSQL 9.0.23 · On AIX, use -Wl,-brtllib link option to allow symbols to be resolved at runtime

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Avoid use of inline functions when compiling with 32-bit xlc, due to compiler bugs
• Same change PostgreSQL 9.3.10 · Avoid use of inline functions when compiling with 32-bit xlc, due to compiler bugs
• Same change PostgreSQL 9.2.14 · Avoid use of inline functions when compiling with 32-bit xlc, due to compiler bugs
• Same change PostgreSQL 9.0.23 · Avoid use of inline functions when compiling with 32-bit xlc, due to compiler bugs

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Use librt for sched_yield() when necessary, which it is on some Solaris versions
• Same change PostgreSQL 9.3.10 · Use librt for sched_yield() when necessary, which it is on some Solaris versions
• Same change PostgreSQL 9.2.14 · Use librt for sched_yield() when necessary, which it is on some Solaris versions
• Same change PostgreSQL 9.0.23 · Use librt for sched_yield() when necessary, which it is on some Solaris versions

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Fix Windows install.bat script to handle target directory names that contain spaces
• Same change PostgreSQL 9.3.10 · Fix Windows install.bat script to handle target directory names that contain spaces
• Same change PostgreSQL 9.2.14 · Fix Windows install.bat script to handle target directory names that contain spaces
• Same change PostgreSQL 9.0.23 · Fix Windows install.bat script to handle target directory names that contain spaces

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · Make the numeric form of the PostgreSQL version number (e.g., 90405) readily available to extension Makefiles, as a variable named VERSION_NUM
• Same change PostgreSQL 9.3.10 · Make the numeric form of the PostgreSQL version number (e.g., 90405) readily available to extension Makefiles, as a variable named VERSION_NUM
• Same change PostgreSQL 9.2.14 · Make the numeric form of the PostgreSQL version number (e.g., 90405) readily available to extension Makefiles, as a variable named VERSION_NUM
• Same change PostgreSQL 9.0.23 · Make the numeric form of the PostgreSQL version number (e.g., 90405) readily available to extension Makefiles, as a variable named VERSION_NUM

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.

• Same change PostgreSQL 9.4.5 · 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.
• Same change PostgreSQL 9.3.10 · 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.
• Same change PostgreSQL 9.2.14 · 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.
• Same change PostgreSQL 9.0.23 · 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.

“Same change” requires complete matching evidence. “Related commits” can cover independent changes, a partial backport, or a follow-up correction; each release keeps its own explanation.