From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Chris Redekop <chris(at)replicon(dot)com> |
Cc: | Florian Pflug <fgp(at)phlo(dot)org>, Daniel Farina <daniel(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot Backup with rsync fails at pg_clog if under load |
Date: | 2011-10-26 08:45:32 |
Message-ID: | CA+U5nMK+Ek4Ef9Kjit9KuaxY=Z2=Oojy=yRDGQXLTQnNA15rvQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 25, 2011 at 10:06 PM, Chris Redekop <chris(at)replicon(dot)com> wrote:
>> Chris, can you rearrange the backup so you copy the pg_control file as
>> the first act after the pg_start_backup?
> I tried this and it doesn't seem to make any difference.
It won't, that was a poor initial diagnosis on my part.
> I also tried the
> patch and I can no longer reproduce the subtrans error
Good
>, however instead it
> now it starts up, but never gets to the point where it'll accept
> connections. It starts up but if I try to do anything I always get "FATAL:
> the database system is starting up"...even if the load is removed from the
> primary, the standby still never finishes "starting up".
...
> 2011-10-25 13:43:25.019 MDT [15072]: [14-1] LOG: consistent state delayed
> because recovery snapshot incomplete
...
This is a different problem and has already been reported by one of
your colleagues in a separate thread, and answered in detail by me
there. There is no bug related to this error message.
From here, it looks like the published fixes the originally reported problem.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-10-26 09:38:14 | Re: TOAST versus VACUUM, or "missing chunk number 0 for toast value" identified |
Previous Message | Shigeru Hanada | 2011-10-26 08:26:00 | Re: pgsql_fdw, FDW for PostgreSQL server |