"Peter Geoghegan" <peter.geoghegan86 at gmail.com> writes:
> 1. As I've said, my current set up has slightly different versions of
> slony-I and PostgreSQL. Will this be problematic? Will it prove
> essential, or prudent to harmonise versions?

Varying versions of Slony-I *WILL* bite you; each cluster MUST use an
identical version of Slony-I across *ALL* the databases in the
cluster.  Slony-I does not accept ANY variation in version numbering;
it will reject connecting to databases any time the slon finds the
database is configured for a different version.

On the other hand, Slony-I will accomodate multiple PostgreSQL
releases.

> 2. According to the "Slon daemons" section of the Slony documentation,
> "On Windows. when running as a service things are slightly different.
> One slon service is installed, and a separate configuration file
> registered for each node to be serviced by that machine. The main
> service then manages the individual slons itself". Would it be
> possible to control the entire cluster through this one Windows/master
> based slon process, with no trace of Slony on the slaves other then
> the triggers and so on that the Slony configuration script leaves in
> the node's database?

You MUST have the appropriate version of Slony-I built into each
server's PostgreSQL build.
-- 
output = reverse("gro.mca" "@" "enworbbc")
http://www3.sympatico.ca/cbbrowne/nonrdbms.html
Rules of the Evil Overlord #12. "One of my advisors will be an average
five-year-old child. Any flaws in my plan that he is able to spot will
be corrected before implementation.  <http://www.eviloverlord.com/>