| From: | "John Lister" <john(dot)lister-ps(at)kickstone(dot)com> |
|---|---|
| To: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | recovery lag question |
| Date: | 2009-11-12 18:40:32 |
| Message-ID: | 9D725B643488412094866BF3ADA3DA38@squarepi.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi, I've set up a warm standby box with postgresql 8.3.8 and pg_standby. Everything seems to be ok, the wal files are being copied across and being processed during the recovery as you'd expect but I have one question. The recovery seems to be processing the final wal files at the same rate as they are generated, which is approximately every 6 minutes. This means that it is currently lagging behind the primary by about 3 hours. I assumed that the recovery would process the wal files as fast as possible until it caught up and then waited, there appears to be no load on the secondary server so I'm guessing it is sat waiting but i may be wrong. Is this the correct behaviour or is something else going on?
Thanks
John
--
Got needs? Get Goblin'! - http://www.pricegoblin.co.uk/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-11-12 20:01:26 | Re: recovery is stuck when children are not processing SIGQUIT from previous crash |
| Previous Message | John Lister | 2009-11-12 18:04:30 | recovery lag question |