Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: Alexey Vasiliev <leopard_ne(at)inbox(dot)ru>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: add recovery_timeout option to control timeout of restore_command nonzero status code
Date: 2014-11-04 00:55:02
Message-ID: CAFcNs+oVGcvC1c3x3sa6aM1jkFyVEKfosL_ikHm+q4jeJxv7GA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 3, 2014 at 7:25 PM, Alexey Vasiliev <leopard_ne(at)inbox(dot)ru> wrote:
>
>
>
>
> Mon, 3 Nov 2014 19:18:51 -0200 от Fabrízio de Royes Mello <
fabriziomello(at)gmail(dot)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,

[1] https://commitfest.postgresql.org/action/commitfest_view?id=25

--
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-11-04 00:59:23 Re: BRIN indexes - TRAP: BadArgument
Previous Message Josh Berkus 2014-11-04 00:49:36 pg_multixact not getting truncated