From: Jeff Davis <pgsql@j-davis.com>
To: Adam Tistler <atistler@gmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: timeline X of the primary does not match recovery target timeline Y
Date: Thu, 20 Oct 2011 10:08:45 -0700
Message-ID: <1319130525.16256.72.camel@jdavis> (raw)
In-Reply-To: <D5696AC8-3F79-4EBF-98FE-E0DF0A66AEDA@gmail.com>
References: <34F74A50-6132-4603-8133-447B2AEF9953@gmail.com>
<1319126408.16256.66.camel@jdavis>
<D5696AC8-3F79-4EBF-98FE-E0DF0A66AEDA@gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: pgsql@j-davis.com, atistler@gmail.com, pgsql-general@postgresql.org
Subject: Re: timeline X of the primary does not match recovery target timeline Y
In-Reply-To: <1319130525.16256.72.camel@jdavis>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox