On Tue, May 30, 2006 at 03:52:14PM -0700, elein wrote:
> > 
> > 4) Stampeding Slony. If for any reason Slony is unable to complete the
> > replication work available within the timeframe allotted (5 minutes I
> > think), Slony will abandon the first connection and establish a new one
> > to retry.
> 
> Exactly what "replication work" do you mean?  One table? All tables being copied?
> In my situation I have 6500*5 + 100 tables to copy.  No way is that going to be
> completed in 5 minutes no matter that the tables are small.  (And no
> I did not design the schema :)

That isn't the initial COPY, for sure, because none of ours will
finish the COPY in 5 mins, either.  I suspect Rod means that there is
a time limit on how long a snapshot-application process runs.  It
can't be 5 mins, though, or we'd run into this after the initial
COPY.  Chris, can you shed more light on this one?

> Are you saying slony won't handle databases of >100GB?  Or tables? 
> If the database is larger than that, exactly what patches should be added 
> for exactly what result?  For the most part I am doing production work and never apply 
> patches not in the main release for obvious reasons.  If there are crucial 
> ones, though, I need more details.

Rod sent some observations about group size (and a patch) to the list
oh, about a month ago?

A

-- 
Andrew Sullivan  | ajs at crankycanuck.ca
Unfortunately reformatting the Internet is a little more painful 
than reformatting your hard drive when it gets out of whack.
		--Scott Morris