From: | Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Resetting crash time of background worker |
Date: | 2015-03-23 02:55:01 |
Message-ID: | CAJ3gD9cKBjac-AB-JfWfO3=pvetFLvda4eSmcGy6eN+5LeFMVg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 17 March 2015 at 19:12, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Mar 17, 2015 at 1:33 AM, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)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 it
> is
> > not flagged BGW_NEVER_RESTART.
>
> I think you're right, and I think we should do the second of those.
> Thanks for tracking this down.
>
Thanks. Attached a patch accordingly. Put this into the June 2015
commitfest.
Attachment | Content-Type | Size |
---|---|---|
reset_crashtimes_fix.patch | text/x-patch | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-03-23 03:00:45 | Re: Zero-padding and zero-masking fixes for to_char(float) |
Previous Message | Bruce Momjian | 2015-03-23 02:53:12 | Re: Zero-padding and zero-masking fixes for to_char(float) |