| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Streaming replication, retrying from archive |
| Date: | 2010-01-14 14:15:14 |
| Message-ID: | 4B4F26F2.3060001@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Imagine this scenario:
1. Master is up and running, standby is connected and streaming happily
2. Network goes down, connection is broken.
3. Standby falls behind a lot. Old WAL files that the standby needs are
archived, and deleted from master.
4. Network is restored. Standby reconnects
5. Standby will get an error because the WAL file it needs is not in the
master anymore.
What will currently happen is:
6, Standby retries connecting and failing indefinitely, until the admin
restarts it.
What we would *like* to happen is:
6. Standby fetches the missing WAL files from archive, then reconnects
and continues streaming.
Can we fix that?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boszormenyi Zoltan | 2010-01-14 14:15:49 | Re: patch to implement ECPG side tracing / tracking ... |
| Previous Message | Matteo Beccati | 2010-01-14 14:08:22 | Re: mailing list archiver chewing patches |