On Thu, Feb 23, 2012 at 10:38 AM, francescoboccacci at libero.it
<francescoboccacci at libero.it> wrote:
> Hi,
> Currently I have a slony replica with one master and one slave. I need to have
> an additional slave on my system.
> I cannot stop the master to create a backup (it requires a lot of time), so my
> question is: is it possible with slony to populate the new slave database and
> sync it?
> With the single master slave I have till now, I started the cluster after
> populating the slave database with the same data of the master and it works
> fine.

Well, when you populated the *first* slave database, that didn't
require any outage on the origin node, did it?

You simply need to:
a) Populate the new database with the *schema* from the master.  There
is no need to capture the data; Slony will delete the data anyways.
   "pg_dump -s" should do the job.
   You'll want to exclude the schema that Slony creates, or drop it
from the new database, if it got loaded
b) STORE NODE to indicate the new node
c) Start up slon for the new node
d) SUBSCRIBE SET against each set that you want on the new node

None of those steps involve an outage of the "master" database.