| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PITR potentially broken in 9.2 |
| Date: | 2012-12-05 14:54:17 |
| Message-ID: | CA+U5nMLFUiDdn7fb8umPXDEfLEYhcnxoX88Cv2U_bkTC6cLmtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 5 December 2012 14:33, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> Independent of this patch, I am slightly confused about the whole stop
> logic. Isn't the idea that you can stop/start/stop/start/... recovery?
> Because if !recoveryApply we break out of the whole recovery loop and
> are done with things.
You can, but by shutting down server, updating recovery target, then
restarting server.
That's not a beautiful design, its just waiting for someone to make
recovery targets changeable, which is best done when recovery.conf
parameters are in postgresql.conf
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-12-05 15:25:47 | Re: PostgreSQL v8.1.11 compatibility with OS 2008 R2 |
| Previous Message | Andres Freund | 2012-12-05 14:39:07 | Re: PITR potentially broken in 9.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cédric Villemain | 2012-12-05 14:58:31 | Re: Review: Dumping an Extension's Script |
| Previous Message | Andres Freund | 2012-12-05 14:39:07 | Re: PITR potentially broken in 9.2 |