| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Adam Tistler <atistler(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: timeline X of the primary does not match recovery target timeline Y |
| Date: | 2011-10-20 17:08:45 |
| Message-ID: | 1319130525.16256.72.camel@jdavis |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general |
On Thu, 2011-10-20 at 12:45 -0400, Adam Tistler wrote:
> Yes you understood correctly. Would the same apply for a hot standby situation?
Right. Hot standby just means that you can query (read-only) an instance
that's still in recovery.
Basically, going from recovery mode (or hot standby, which is also
recovery mode) to "up" (that is, can accept write queries and operate
normally) is not a reversible process. You have to make a new base
backup of another system to start recovering again.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Steben | 2011-10-20 18:16:08 | check_postgres monitor by Bucardo - any opinions? |
| Previous Message | Adam Tistler | 2011-10-20 16:45:43 | Re: timeline X of the primary does not match recovery target timeline Y |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Harding | 2011-10-20 17:12:38 | Extraneous Files |
| Previous Message | Adam Tistler | 2011-10-20 16:45:43 | Re: timeline X of the primary does not match recovery target timeline Y |