Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E3D416329C9 for ; Mon, 23 Aug 2010 16:57:43 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 42927-07 for ; Mon, 23 Aug 2010 19:57:36 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by mail.postgresql.org (Postfix) with ESMTP id 2F4BC632471 for ; Mon, 23 Aug 2010 16:57:36 -0300 (ADT) Received: by vws3 with SMTP id 3so5548505vws.19 for ; Mon, 23 Aug 2010 12:57:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=+qYvKAUAo7SLmDB3nbm+GJUV/dMSjJzWI9AJ24IO7aI=; b=SwSLxWVd4ulEWmjBUWijtZWkjbWAaT0nxH/i+Lb44ESO8xp036W7XYVRtEhOs5+K3I MxZx5i6yGsNRKUab5Ck60+neEd/FT1xS6Bpl2R6fvCDOb65dhaiOWb5RwGJUdJ1lQECC r/+Tx/6kSUrrttz43bwszxWJMinXSn/11d8Oc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=E7y86Zx55ihG+YguRE1iZAeIUKfNJ6JKBCBi3/4Uva/28pc/GVrpsn+EpCeXptcFyu UAJoAdOhuEC0++OdLKbvQW7ReyWsTBRILYDE7QPrstQy23tyYEstMJcb5fU7SyP5TlU/ LYk4+xieSml3s2O/tDDSwc2vLc/91nCb9rqN8= MIME-Version: 1.0 Received: by 10.220.85.145 with SMTP id o17mr3535292vcl.51.1282593454986; Mon, 23 Aug 2010 12:57:34 -0700 (PDT) Received: by 10.220.49.161 with HTTP; Mon, 23 Aug 2010 12:57:34 -0700 (PDT) In-Reply-To: <10238.1282591075@sss.pgh.pa.us> References: <10238.1282591075@sss.pgh.pa.us> Date: Mon, 23 Aug 2010 12:57:34 -0700 Message-ID: Subject: Re: Error while setting up streaming replication, postgres 9.0-beta 4 From: fazool mein To: Tom Lane Cc: pgsql-admin@postgresql.org Content-Type: multipart/alternative; boundary=0016e647ec6e469797048e830f02 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.42 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FS_REPLICA=3.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SARE_SPEC_REPLICA=0.72 X-Spam-Level: ** X-Archive-Number: 201008/153 X-Sequence-Number: 35402 --0016e647ec6e469797048e830f02 Content-Type: text/plain; charset=ISO-8859-1 Great! I made the base backup again as you said, and its working now. Thanks. On Mon, Aug 23, 2010 at 12:17 PM, Tom Lane wrote: > fazool mein writes: > > I'm trying to test streaming replication. I set up a primary and > secondary. > > The primary starts normal, but when I start the standby, it doesn't start > > up. The log looks like this: > > > LOG: database system was interrupted while in recovery at log time > > 2010-08-23 13:30:43 EDT > > HINT: If this has occurred more than once some data might be corrupted > and > > you might need to choose an earlier recovery target. > > LOG: entering standby mode > > WARNING: WAL was generated with wal_level=minimal, data may be missing > > HINT: This happens if you temporarily set wal_level=minimal without > taking > > a new base backup. > > FATAL: hot standby is not possible because wal_level was not set to > > "hot_standby" on the master server > > HINT: Either set wal_level to "hot_standby" on the master, or turn off > > hot_standby here. > > LOG: startup process (PID 5875) exited with exit code 1 > > LOG: aborting startup due to startup process failure > > > > Note that I have checked multiple times that 'wal_level' is set to > > 'hot_standby' on the primary, > > You need to do that *before* taking your base backup. The WARNING above > indicates that the backup was taken with an inadequate wal_level > setting. > > regards, tom lane > --0016e647ec6e469797048e830f02 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Great! I made the base backup again as you said, and its working now.
Th= anks.


On Mon, Aug 23, 2010 at 12:17 P= M, Tom Lane <tgl@= sss.pgh.pa.us> wrote:
fazool mein <fazoolmein@gmail.c= om> writes:
> I'm trying to test streaming replication. I set up a primary and s= econdary.
> The primary starts normal, but when I start the standby, it doesn'= t start
> up. The log looks like this:

> LOG: =A0database system was interrupted while in recovery at log time<= br> > 2010-08-23 13:30:43 EDT
> HINT: =A0If this has occurred more than once some data might be corrup= ted and
> you might need to choose an earlier recovery target.
> LOG: =A0entering standby mode
> WARNING: =A0WAL was generated with wal_level=3Dminimal, data may be mi= ssing
> HINT: =A0This happens if you temporarily set wal_level=3Dminimal witho= ut taking
> a new base backup.
> FATAL: =A0hot standby is not possible because wal_level was not set to=
> "hot_standby" on the master server
> HINT: =A0Either set wal_level to "hot_standby" on the master= , or turn off
> hot_standby here.
> LOG: =A0startup process (PID 5875) exited with exit code 1
> LOG: =A0aborting startup due to startup process failure


> Note that I have checked multiple times that 'wal_level' is se= t to
> 'hot_standby' on the primary,

You need to do that *before* taking your base backup. =A0The WARNING = above
indicates that the backup was taken with an inadequate wal_level
setting.

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0regards, tom lane

--0016e647ec6e469797048e830f02--