| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |
| Date: | 2011-03-08 00:20:27 |
| Message-ID: | AANLkTimG+Wvyzo7nB8PniDLCKijGxxZRRHFFtW+sqgc4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, Feb 8, 2011 at 11:00 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> On Tue, Feb 8, 2011 at 1:30 PM, 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.
>>
>
> I guess that new parameter should also be in recovery.conf.sample, right?
>
This one is still not in recovery.conf.sample
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-03-08 02:36:09 | Re: pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |
| Previous Message | Peter Eisentraut | 2011-03-07 21:53:09 | pgsql: Report Python errors from iterators with PLy_elog |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-03-08 00:41:10 | Re: ModifyTable EXPLAIN Node |
| Previous Message | Tom Lane | 2011-03-08 00:15:28 | Re: Theory of operation of collation patch |