Jan Wieck wrote:
  > so you have PostgreSQL installed in the usual RPM locations as well as
> in the default source-tarball locations, which is the usual result of 
> unpacking the PostgreSQL source tarball, doing configure (without 
> options) and "make install" on a RedHat box that has PostgreSQL RPM's 
> installed. This probably applies to other distributions as well.

	Ok, NOW I see the problem.  I had already installed PostgreSQL manually 
from source.  I wanted to install Slony from FreeBSD Ports because I 
ASSumed it would auto-detect that Postgres was already installed and be 
easier.  I guess I was wrong!  Here's what happened:

	Of course Postgres is a requisite for Slony, so installing Slony from 
the FreeBSD ports resulted in the installation of the Postgres port as 
well!  That's how I ended up with 2 copies.

	So to fix this mess I'm going to have to uninstall the Postgres and 
Slony ports, then compile & install Slony manually.  Yipee!

-j