From: Ray Stell <stellr@cns.vt.edu>
To: pgsql-admin@postgresql.org
Subject: Re: PostgreSQL 9.0.3 streaming replication failure
Date: Wed, 9 Feb 2011 09:28:18 -0500
Message-ID: <20110209142818.GA30017@cns.vt.edu> (raw)
In-Reply-To: <20110209135548.GA27471@cns.vt.edu>
References: <20110209135548.GA27471@cns.vt.edu>
On Wed, Feb 09, 2011 at 08:55:48AM -0500, Ray Stell wrote:
> I had set up this streaming replication pair of systems a few days ago and
> everything seemed pretty happy as changes were being replicated. I set
> it up without wal archiving turned up. The backup log this morning caught
> my eye. I find the standby reports to have activated itself.
>
> I don't see anything in the postmaster logs on this event.
>
> The backup log caught my eye:
> -------------------------------
> pg_start_backup
> -----------------
> 1/E0000020
> (1 row)
>
> NOTICE: WAL archiving is not enabled; you must ensure that all required WAL segments are copied through other means to complete the backup
> pg_stop_backup
> ----------------
> 1/E00000C4
> (1 row)
my bad, this was a path issue, I was using a v8 pg_controldata cmd.
the v9 pg_controldata looks good. Sorry.
This does not explain the backup/wal archive msg, however. Is that
msg normal for a streaming rep set up?
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: stellr@cns.vt.edu
Subject: Re: PostgreSQL 9.0.3 streaming replication failure
In-Reply-To: <20110209142818.GA30017@cns.vt.edu>
* 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