On Monday September 6 2004 4:20, Christopher Browne wrote:
> And the real problem would most likely come in the initial "seeding."
> When you provision a new subscriber, it has to take on _all_ of the data
> then sitting at its provider, all in one transaction.  That takes a
> while, across a slow link, and if that link is not sufficiently reliable,
> you might never get the first "sync."

Our typical DB is around 10GB.  Do I understand correctly that the first 
seeding transfer will include all of the 10GB in one very large, very long 
transaction on the slave?  Any concerns about that much data going across?  

And the path traveled is from provider pgsql to provider slon to subscriber 
slon to subscriber pgsql?  Any concerns there about memory needs?  Or is it 
pipelined in transfer?

Ed