{"push_id":724058609,"size":6,"distinct_size":6,"ref":"refs/heads/REL9_2_STABLE","head":"a24ceea4b311146d41e3bd5b8e0df7176113675f","before":"ebe601c4daf3cdcde5156d941a6ae880ab94c7cd","commits":[{"sha":"458ccbf2b3a9a8566a405368825954cf99b8dbef","author":{"email":"1db01d43e08596f43a65fb393d969b98ee5b4dc6@leadboat.com","name":"Noah Misch"},"message":"Fix null pointer dereference in \"\\c\" psql command.\n\nThe psql crash happened when no current connection existed.  (The second\nnew check is optional given today's undocumented NULL argument handling\nin PQhost() etc.)  Back-patch to 9.0 (all supported versions).","distinct":true,"url":"https://api.github.com/repos/Distrotech/postgresql/commits/458ccbf2b3a9a8566a405368825954cf99b8dbef"},{"sha":"f7b3300384c1f726e4c1fe34ecec409826c2cdef","author":{"email":"1db01d43e08596f43a65fb393d969b98ee5b4dc6@leadboat.com","name":"Noah Misch"},"message":"Replace use of \"diff -q\".\n\nPOSIX does not specify the -q option, and many implementations do not\noffer it.  Don't bother changing the MSVC build system, because having\nnon-GNU diff on Windows is vanishingly unlikely.  Back-patch to 9.2,\nwhere this invocation was introduced.","distinct":true,"url":"https://api.github.com/repos/Distrotech/postgresql/commits/f7b3300384c1f726e4c1fe34ecec409826c2cdef"},{"sha":"8dc8a31a3a036830bcffe2c803688b60ebd67bfc","author":{"email":"ac1e0af1ee8efe15f889b38482e897ff7d0f0432@iki.fi","name":"Heikki Linnakangas"},"message":"Fix another broken link in documentation.\n\nTom fixed another one of these in commit 7f32dbcd, but there was another\nalmost identical one in libpq docs. Per his comment:\n\nHP's web server has apparently become case-sensitive sometime recently.\nPer bug #13479 from Daniel Abraham.  Corrected link identified by Alvaro.","distinct":true,"url":"https://api.github.com/repos/Distrotech/postgresql/commits/8dc8a31a3a036830bcffe2c803688b60ebd67bfc"},{"sha":"97122b8a8e592d71408addce98aa3ac66f56fdc3","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix postmaster's handling of a startup-process crash.\n\nOrdinarily, a failure (unexpected exit status) of the startup subprocess\nshould be considered fatal, so the postmaster should just close up shop\nand quit.  However, if we sent the startup process a SIGQUIT or SIGKILL\nsignal, the failure is hardly \"unexpected\", and we should attempt restart;\nthis is necessary for recovery from ordinary backend crashes in hot-standby\nscenarios.  I attempted to implement the latter rule with a two-line patch\nin commit 442231d7f71764b8c628044e7ce2225f9aa43b67, but it now emerges that\nthat patch was a few bricks shy of a load: it failed to distinguish the\ncase of a signaled startup process from the case where the new startup\nprocess crashes before reaching database consistency.  That resulted in\ninfinitely respawning a new startup process only to have it crash again.\n\nTo handle this properly, we really must track whether we have sent the\n*current* startup process a kill signal.  Rather than add yet another\nad-hoc boolean to the postmaster's state, I chose to unify this with the\nexisting RecoveryError flag into an enum tracking the startup process's\nstate.  That seems more consistent with the postmaster's general state\nmachine design.\n\nBack-patch to 9.0, like the previous patch.","distinct":true,"url":"https://api.github.com/repos/Distrotech/postgresql/commits/97122b8a8e592d71408addce98aa3ac66f56fdc3"},{"sha":"349ce2870f1039b83811af0c640fe58efe16e3f7","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Improve documentation about array concat operator vs. underlying functions.\n\nThe documentation implied that there was seldom any reason to use the\narray_append, array_prepend, and array_cat functions directly.  But that's\nnot really true, because they can help make it clear which case is meant,\nwhich the || operator can't do since it's overloaded to represent all three\ncases.  Add some discussion and examples illustrating the potentially\nconfusing behavior that can ensue if the parser misinterprets what was\nmeant.\n\nPer a complaint from Michael Herold.  Back-patch to 9.2, which is where ||\nstarted to behave this way.","distinct":true,"url":"https://api.github.com/repos/Distrotech/postgresql/commits/349ce2870f1039b83811af0c640fe58efe16e3f7"},{"sha":"a24ceea4b311146d41e3bd5b8e0df7176113675f","author":{"email":"ffeaa947aef224da9ba99b6a18bdd74288df0e3e@sss.pgh.pa.us","name":"Tom Lane"},"message":"Fix assorted memory leaks.\n\nPer Coverity (not that any of these are so non-obvious that they should not\nhave been caught before commit).  The extent of leakage is probably minor\nto unnoticeable, but a leak is a leak.  Back-patch as necessary.\n\nMichael Paquier","distinct":true,"url":"https://api.github.com/repos/Distrotech/postgresql/commits/a24ceea4b311146d41e3bd5b8e0df7176113675f"}]}