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 Raw
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  (Alexey Vasiliev <leopard_ne@inbox.ru>)
List pgsql-hackers
<div dir="ltr"><div class="gmail_extra">><br />> Should I change my patch and send it by email? And also as I
understandI should change message ID for <a
href="https://commitfest.postgresql.org/action/patch_view?id=1636">https://commitfest.postgresql.org/action/patch_view?id=1636</a>,
isn'tit?<br />><br /><br /></div><div class="gmail_extra">You should just send another version of your patch by
emailand add a new "comment" to commit-fest using the "Patch" comment type.<br /></div><div class="gmail_extra"><br
/></div><divclass="gmail_extra">Regards,<br /></div><div class="gmail_extra"><br />--<br />Fabrízio de Royes Mello<br
/>Consultoria/CoachingPostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog: <a
href="http://fabriziomello.github.io">http://fabriziomello.github.io</a><br/>>> Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a><br/>>> Github: <a
href="http://github.com/fabriziomello">http://github.com/fabriziomello</a></div></div>

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