Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,
Date: 2011-02-09 03:50:04
Message-ID: AANLkTi=oadik7ySXsHTZgTE29x+UA=fcC2sCNMTw3D=4@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, Feb 9, 2011 at 3:30 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Basic Recovery Control functions for use in Hot Standby. Pause, Resume,
> Status check functions only. Also, new recovery.conf parameter to
> pause_at_recovery_target, default on.

Why did you change the default to on? This would surprise people who are
used to PITR.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Jaime Casanova 2011-02-09 04:00:58 Re: pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,
Previous Message Simon Riggs 2011-02-08 23:23:57 Re: pgsql: Suppress some compiler warnings in recent commits.

Browse pgsql-hackers by date

  From Date Subject
Next Message Hitoshi Harada 2011-02-09 03:52:26 Re: pl/python do not delete function arguments
Previous Message Tom Lane 2011-02-09 03:43:29 Re: Extensions versus pg_upgrade