Marcel Inowe wrote:
> Hi all,
>
> I?m trying to configure one replication with Slony-I, and I?m not 
> getting.... I?m with this doubt. I don?t know how to create the Schema with the 
> tables, function and sequence that Slony needs to work. Somebody knows ?
> I don?t know if I?m configuring wrong, I?m following a tutorial that I 
> found in the Net, the tutorial is doing like this:
>
> PGMAIN=/usr/local/pgsql746-freebsd-2005-04-01 \
> ../configure \
> --prefix=$PGMAIN \
> --bindir=$PGMAIN/bin \
> --datadir=$PGMAIN/share \
> --libdir=$PGMAIN/lib \
> --with-pgconfigdir=$PGMAIN/bin \
> --with-pgbindir=$PGMAIN/bin \
> --with-pgincludedir=$PGMAIN/include \
> --with-pglibdir=$PGMAIN/lib \
> --with-pgsharedir=$PGMAIN/share
>
> My doubt is here, what I need to put in the PGMAIN ? Is the PostgreSQL 
> installation directory ? or is the data directory ? because I left 
> separated.
>
> If somebody can help me I thanks.
>
>   
With recent versions, all you should need to specify is the
--with-pgconfigdir parameter, *possibly* more if you want to install
documentation and such.  All the other options should normally not be
needed, at least not on Unix-like systems.  (I'm not sure how much the
Windows port can get out of pg_config.  Perhaps Windows porters can
comment on that?  It's probably useful to know...)

- The binaries are normally put alongside the PG binaries (psql,
pg_dump, and such)

- Libraries *have to be* in the ../lib directory used by the PG install

- Other shared bits *have to be* in the ../share directory used by the
PG install

Generally, this means that $PGMAIN is the "main directory" where your
PostgreSQL installation "lives."

It is in principle *possible* for the PostgreSQL installation to be
configured to stow components in diverse places.  Thus, binaries might
be in /usr/bin, libs in /usr/lib/postgresql/pg746, shared things in
/usr/share/postgresql/pg746, and such like, in which case "$PGMAIN"
doesn't actually have any meaning.

If you specify --with-pgconfigdir to point to the directory where the
program pg_config resides, the Slony-I configure script will consult
pg_config to determine the various locations that it needs to stow
things.  --prefix, --bindir, --datadir, --libdir, and
--with-pg-equivalents-to-those become pretty much irrelevant.

I have changed the docs to reflect this in CVS.  (Aside:  This is NOT
reason for us to defer to an RC5 :-); if RC4 becomes 1.2.0, this will
get drawn into what is tagged as 1.2.0.)