Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code
Date
Msg-id CAFcNs+oVGcvC1c3x3sa6aM1jkFyVEKfosL_ikHm+q4jeJxv7GA@mail.gmail.com
Whole thread Raw
In response to Re[3]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code  (Alexey Vasiliev <leopard_ne@inbox.ru>)
Responses Re[2]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code  (Alexey Vasiliev <leopard_ne@inbox.ru>)
List pgsql-hackers


On Mon, Nov 3, 2014 at 7:25 PM, Alexey Vasiliev <leopard_ne@inbox.ru> wrote:
>
>
>
>
> Mon, 3 Nov 2014 19:18:51 -0200 от Fabrízio de Royes Mello <fabriziomello@gmail.com>:
> >
> > >
> > > Should I change my patch and send it by email? And also as I understand I should change message ID for  https://commitfest.postgresql.org/action/patch_view?id=1636 , isn't it?
> > >
> >
> > You should just send another version of your patch by email and add a new "comment" to commit-fest using the "Patch" comment type.
>
>
> Added new patch.
>

And you should add the patch to an open commit-fest not to an in-progress. The next opened is 2014-12 [1].


Regards,

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: pg_multixact not getting truncated
Next
From: Alvaro Herrera
Date:
Subject: Re: BRIN indexes - TRAP: BadArgument