Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 6E038B5DC20 for ; Thu, 20 Oct 2011 14:08:50 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 70356-09 for ; Thu, 20 Oct 2011 17:08:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.8.0-rc2 Received: from mail-iy0-f174.google.com (mail-iy0-f174.google.com [209.85.210.174]) by mail.postgresql.org (Postfix) with ESMTP id 4B826B5DC00 for ; Thu, 20 Oct 2011 14:08:44 -0300 (ADT) Received: by iaek3 with SMTP id k3so3634819iae.19 for ; Thu, 20 Oct 2011 10:08:43 -0700 (PDT) Received: by 10.42.157.3 with SMTP id b3mr19466094icx.44.1319130523629; Thu, 20 Oct 2011 10:08:43 -0700 (PDT) Received: from [192.168.1.102] (c-69-181-249-16.hsd1.ca.comcast.net. [69.181.249.16]) by mx.google.com with ESMTPS id jm11sm25187202ibb.1.2011.10.20.10.08.41 (version=SSLv3 cipher=OTHER); Thu, 20 Oct 2011 10:08:41 -0700 (PDT) Message-ID: <1319130525.16256.72.camel@jdavis> Subject: Re: timeline X of the primary does not match recovery target timeline Y From: Jeff Davis To: Adam Tistler Cc: pgsql-general@postgresql.org Date: Thu, 20 Oct 2011 10:08:45 -0700 In-Reply-To: References: <34F74A50-6132-4603-8133-447B2AEF9953@gmail.com> <1319126408.16256.66.camel@jdavis> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.0- Content-Transfer-Encoding: 7bit Mime-Version: 1.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-5 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201110/751 X-Sequence-Number: 181223 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