From: | Chris Redekop <chris(at)replicon(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(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 15:36:56 |
Message-ID: | CAC2SuRL8hjcSpWdyVAQpStJ6bw6FyCGUPKkesmCgMX-a_JHmTQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> And I think they also reported that if they didn't run hot standby,
> but just normal recovery into a new master, it didn't have the problem
> either, i.e. without hotstandby, recovery ran, properly extended the
> clog, and then ran as a new master fine.
Yes this is correct...attempting to start as hotstandby will produce the
pg_clog error repeatedly and then without changing anything else, just
turning hot standby off it will start up successfully.
> This fits the OP's observation ob the
> problem vanishing when pg_start_backup() does an immediate checkpoint.
Note that this is *not* the behaviour I'm seeing....it's possible it happens
more frequently without the immediate checkpoint, but I am seeing it happen
even with the immediate checkpoint.
> 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.
Excellent...I will continue this discussion in that thread.
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-10-26 15:42:52 | Re: Range Types - typo + NULL string constructor |
Previous Message | Kohei KaiGai | 2011-10-26 14:57:48 | Re: pgsql_fdw, FDW for PostgreSQL server |