snacktime <snacktime at gmail.com> writes:
> Before I dig in and start learning this beast, I thought I would
> make sure there aren't any obvious reasons why slony wouldn't work
> for us.  We keep up to 5000 or so clients per db server, with each
> client having their own set of tables in their own schema.  The
> tables are the same for every client.  Any potential issues with
> using slony in this situation?

Confusion could be a problem.

Having a lot of tables isn't inherently problematic; those that aren't
accessed don't consume much in the way of resources.  There's nothing
that "polls through" them individually.

Having a lot of sequences isn't so good, mind you; those are
essentially handled via polling.  5000 of them (1 per client) means
that each SYNC will process and store 5000 sequence values.

The other notable challenge would be of getting all the schemas and
tables and schemas added to replication.  How do new clients get set
up???
-- 
(format nil "~S@~S" "cbbrowne" "ca.afilias.info")
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)