| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Turning recovery.conf into GUCs |
| Date: | 2013-10-18 16:54:46 |
| Message-ID: | CAJKUy5i5ZfSW2P388pXNDhCxqXvO7a2QiaOX6cj5vHW_veWvjQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Oct 18, 2013 at 11:32 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> exactly as it is now, if it sees the recovery trigger file, then it
>> starts ArchiveRecovery and after it finish delete the file (the only
>> difference) and increment the timeline
>
> OK, so if I'm doing a PITR recovery, I just put the recovery variables
> into postgresql.conf, then?
>
create a recovery trigger file (called standby.enabled in current
patch) in $PGDATA and start the server
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ants Aasma | 2013-10-18 16:55:48 | Re: removing old ports and architectures |
| Previous Message | Stefan Kaltenbrunner | 2013-10-18 16:36:03 | Re: removing old ports and architectures |