Re: Re[2]: [HACKERS] 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: Re[2]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code
Date
Msg-id CAFcNs+qrw9CdjcJ9MOJXPapPdP5GvK9ypXdC7ZHs805B9WiXXA@mail.gmail.com
Whole thread
In response to Re[2]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code  (Alexey Vasiliev <leopard_ne@inbox.ru>)
Responses Re[3]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code
List pgsql-hackers
>
> 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.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: how to handle missing "prove"
Next
From: Tom Lane
Date:
Subject: Re: Repeatable read and serializable transactions see data committed after tx start