Re: Request for vote to move forward with recovery.conf overhaul

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Phil Sorber <phil(at)omniti(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Request for vote to move forward with recovery.conf overhaul
Date: 2013-01-23 11:36:16
Message-ID: 968DCADD-E20B-488F-953A-FF88A490E744@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2013/01/23, at 18:12, Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:

> On 23 January 2013 04:49, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>
>> - recovery.conf is removed (no backward compatibility in this version of the
>> patch)
>
> If you want to pursue that, you know where it leads. No, rebasing a
> rejected patch doesn't help, its just relighting a fire that shouldn't
> ever have been lit.
>
> Pushing to do that out of order is just going to drain essential time
> out of this CF from all of us.
No problem to support both. The only problem I see is if the same parameter is defined in recovery.conf and postgresql.conf, is the priority given to recovery.conf?
--
Michael Paquier
http://michael.otacoo.com
(Sent from my mobile phone)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Etsuro Fujita 2013-01-23 12:05:52 Re: Review : Add hooks for pre- and post-processor executables for COPY and \copy
Previous Message Heikki Linnakangas 2013-01-23 11:03:53 Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)