Re: Streaming rep - why log shipping is necessary?

From: marcin mank <marcin(dot)mank(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Streaming rep - why log shipping is necessary?
Date: 2010-02-25 09:55:48
Message-ID: b1b9fac61002250155u2b52a876h54d01ac8292e17d9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 25, 2010 at 10:08 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> the standby needs to
> fall back to the archive if it falls behind so that the WAL files it
> needs have already been recycled in the master.

Oh, so the master does not have to keep track of the state of the
standbys. That`s a nice design.

> If you're adventurous enough, it's actually possible to set an
> archive_command that checks the status of the standby and returns
> failure as long as the standby still needs the given WAL segment. That
> way the primary doesn't recycle segments that are still needed by the
> standby, and you can get away without restore_command in the standby.

That would be a nice addition to pg_standby, like
pg_standby --check-streaming-standby postgres:qwerty(at)10(dot)0(dot)0(dot)1
--check-streaming-standby postgres:qwerty(at)10(dot)0(dot)0(dot)2:5433

Greetings
Marcin Mańk

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2010-02-25 10:22:24 Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset
Previous Message Magnus Hagander 2010-02-25 09:42:27 Re: Recent vendor SSL renegotiation patches break PostgreSQL