Re: WARM standby with pg_standby

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: Dennis Thrysøe <dth(at)geysirit(dot)dk>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: WARM standby with pg_standby
Date: 2010-04-09 14:19:17
Message-ID: 4BBEF1150200002500030644@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Dennis Thrysøe<dth(at)geysirit(dot)dk> wrote:

> After copying a new dump of the MASTER cluster data and starting
> the SLAVE with this data, I now get:
>
> Database cluster state: in production
> ..
> Minimum recovery ending location: 0/0

Somehow it completed archive recovery and switched over to
production. How are you configured for triggering that? Is there
some triggering file you need to delete before you try again?

> "cp: cannot stat `/psql_archive/00000001.history': No such file
> or directory"

As already mentioned, that's just noise. Ignore that line, as long
as you just see it once per startup.

> By the way, one of these lines each second!
>
> "2010-04-09 09:09:49 IST FATAL: the database system is starting
> up"

Forever, or some fixed number of times?

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2010-04-09 14:22:26 Re: archive_timeout - good indication
Previous Message Kevin Grittner 2010-04-09 14:14:27 Re: database restoration problem- data became incorrect caused by incorrect date in the server