From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Petr Novak <petr(dot)novak23(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: CLOG read problem after pg_basebackup |
Date: | 2015-06-21 21:39:16 |
Message-ID: | 20150621213916.GD4797@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On 2015-01-23 15:31:15 +0100, Petr Novak wrote:
> I'd like to ask for help clarifying an issue I'm having.
>
> I've recently prepared new servers in another datacenter for some of our
> databases which I want to set up as a streaming replicas. There are several
> instances(clusters) with size ranging from 50-150GB. Some of them were set
> up with no issue. Three of them failed to start after pg_basebackup
> completed with:
>
> FATAL: could not access status of transaction 923709700
> DETAIL: Could not read from file "pg_clog/0370" at offset 237568: Success.
>
> (the clog file differed in each case of course..)
How exactly are you starting the the standby after the basebackups? Any
chance you removed backup.label? This sounds like the typical symptoms
of doing that.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-06-22 00:12:42 | Re: INSERT a number in a column based on other columns OLD INSERTs |
Previous Message | litu16 | 2015-06-21 19:28:47 | Re: INSERT a number in a column based on other columns OLD INSERTs |