diff --git a/doc/src/sgml/release-9.3.sgml b/doc/src/sgml/release-9.3.sgml index 95939ee303..2ba89b413a 100644 --- a/doc/src/sgml/release-9.3.sgml +++ b/doc/src/sgml/release-9.3.sgml @@ -106,25 +106,6 @@ Branch: REL9_3_STABLE [fb47de2be] 2014-02-13 19:30:30 -0300 - - - - - Fix multixact freezing of tuples that predate - a pg_upgrade to 9.3 - (Álvaro Herrera) - - - - This oversight would result in complaints such as ERROR: - MultiXactId 11415437 does no longer exist -- apparent wraparound. - - - - Fix race conditions in walsender shutdown logic and walreceiver - SIGHUP signal handler (Tom Lane) + Prevent timeout interrupts from taking control away from mainline + code unless ImmediateInterruptOK is set + (Andres Freund, Tom Lane) + + + + This is a serious issue for any application making use of statement + timeouts, as it could cause all manner of strange failures after a + timeout occurred. We have seen reports of stuck spinlocks, + ERRORs being unexpectedly promoted to PANICs, unkillable backends, + and other misbehaviors. @@ -441,8 +429,23 @@ Branch: REL8_4_STABLE [458b20f2d] 2014-01-31 21:41:09 -0500 - Ensure that signal handlers don't attempt to use - the process's MyProc pointer after it's no longer valid. + Ensure that signal handlers don't attempt to use the + process's MyProc pointer after it's no longer valid. + + + + + + + + Fix race conditions in walsender shutdown logic and walreceiver + SIGHUP signal handler (Tom Lane) @@ -490,25 +493,6 @@ Branch: REL8_4_STABLE [d0070ac81] 2014-01-11 16:35:44 -0500 - - - - - Prevent timeout interrupts from taking control away from mainline - code unless ImmediateInterruptOK is set - (Andres Freund, Tom Lane) - - - - This was initially reported as a stuck spinlock failure, - but many other misbehaviors are possible after a statement timeout. - - -