Re: Streaming replication, retrying from archive
Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Dimitri Fontaine <dfontaine@hi-media.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Fujii Masao <masao.fujii@gmail.com>, Magnus Hagander <magnus@hagander.net>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-01-21T22:15:25Z
Lists: pgsql-hackers
Dimitri Fontaine wrote: > Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes: > >> Yeah, a lot of that logic and states is completely unnecessary until we >> have a synchronous mode. Even then, it seems complex. >> > > I hope we'll find something less complex, what I proposed is heavily > inspired from londiste (Skytools) table addition to a replication set > (parallel COPY), which works fine. > > >> Here's what I've been hacking: >> > [...] > >> So there's just two states: >> >> 1. Recovering from archive >> 2. Streaming >> >> We start from 1, and switch state at error. >> > > Oh yes that's even more simple! > > >> This gives nice behavior from a user point of view. Standby tries to >> make progress using either the archive or streaming, whichever becomes >> available first. >> > > So tools like pitrtools or walmgr.py will certainly continue being > necessary to use in 9.0, right? > > Right now Streaming Replication does not do your backup for you, which some of the tools (e.g walmgr.py) do... Thinking about walmgr.py for a moment - it should be pretty easy (or possible anyway) to make it use streaming replication for server versions >= 9.0. Cheers Mark