Slony replication

Pedro Doria Meunier wrote:

Hi All,

I would like to implement DB replication with Slony but with a slave
that will not be always available.
The master would have to check first of the slave's availability and
then start syncing...

Is this at all possible, or am I just raving? : )

I am quite new to Slony as well, but one of the first requirements the
docs state is:

Thus, examples of cases where Slony-I probably won't work out well
would include:

* Sites where connectivity is really "flakey"
* Replication to nodes that are unpredictably connected.

So I suspect Slony is not a solution for your effort. See:

http://slony.info/documentation/slonyintro.html#INTRODUCTION

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin

On 08/12/2007 09:51, Pedro Doria Meunier wrote:

I would like to implement DB replication with Slony but with a slave
that will not be always available.
The master would have to check first of the slave's availability and
then start syncing...

Please post this to the Slony-I list: this list is for PgAdmin.

Off the top of my head, I don't think that will work for you - but if
you read the documentation for Slony, I seem to recall that you need a
reasonable degree of availability for Slony to work.

Do read the documentation - it's pretty comprehensive, and will save
bandwidth in the lists.....

Ray.

---------------------------------------------------------------
Raymond O'Donnell, Director of Music, Galway Cathedral, Ireland
rod@iol.ie
---------------------------------------------------------------

On Dec 8, 2007, at 9:21 AM, Geoffrey wrote:

I am quite new to Slony as well, but one of the first requirements
the docs state is:

Thus, examples of cases where Slony-I probably won't work out well
would include:

* Sites where connectivity is really "flakey"
* Replication to nodes that are unpredictably connected.

So I suspect Slony is not a solution for your effort. See:

If your DB doesn't change very much (like a few hundred or thousand
update/insert/delete per day), then slony can work just fine in such a
batch mode. Things break down when you accumulate several hundred
thousand or more changes between times when you're connected.