On Sun, Mar 22, 2015 at 10:55 PM, Amit Khandekar amitdkhan...@gmail.com wrote:
On 17 March 2015 at 19:12, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 17, 2015 at 1:33 AM, Amit Khandekar amitdkhan...@gmail.com
wrote:
I think we either have to retain the knowledge that the worker has
On 17 March 2015 at 19:12, Robert Haas robertmh...@gmail.com wrote:
On Tue, Mar 17, 2015 at 1:33 AM, Amit Khandekar amitdkhan...@gmail.com
wrote:
I think we either have to retain the knowledge that the worker has
crashed
using some new field, or else, we should reset the crash time only if
On Tue, Mar 17, 2015 at 1:33 AM, Amit Khandekar amitdkhan...@gmail.com wrote:
When the postmaster recovers from a backend or worker crash, it resets bg
worker's crash time (rw-rw_crashed_at) so that the bgworker will
immediately restart (ResetBackgroundWorkerCrashTimes).
But resetting
When the postmaster recovers from a backend or worker crash, it resets bg
worker's crash time (rw-rw_crashed_at) so that the bgworker will
immediately restart (ResetBackgroundWorkerCrashTimes).
But resetting rw-rw_crashed_at to 0 means that we have lost the
information that the bgworker had