From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Sergei Kornilov <sk@zsrv.org>
To: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Subject: Re: Continue work on changes to recovery.conf API
Date: Wed, 29 Aug 2018 15:27:00 +0200
Message-ID: <64b6e400-74fa-3b30-5bcf-4d6a1facbf27@2ndquadrant.com> (raw)
In-Reply-To: <3595211530445522@web17o.yandex.ru>
References: <607741529606767@web3g.yandex.ru>
<594281529606887@web2j.yandex.ru>
<3595211530445522@web17o.yandex.ru>
On 01/07/2018 13:45, Sergei Kornilov wrote:
> Commitfest 2018-09 is now open and, as planned, i create one entry: https://commitfest.postgresql.org/19/1711/
> Also i attach new version due merge conflict with HEAD.
Could you please describe in detail what this current patch does?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, sk@zsrv.org
Subject: Re: Continue work on changes to recovery.conf API
In-Reply-To: <64b6e400-74fa-3b30-5bcf-4d6a1facbf27@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox