> I have built slony 1.0.2 with postgres 7.4.5. This needs to be deployed
> on a system other than the one on which is was built. Somebody on our
> team had earlier gotten around the problem of not being able to move a
> postgres install by manually updating the pg_catalog.pg_proc table. But
> it seems like this worked *after* the procs calling external libraries
> were installed. With the slony stuff I can't install the procs until the
> database has been deployed on its target machine, so that hack doesn't
> seem to help me.
>
> Now I'm trying to run a slonik script on the new system, and I am
> getting the following error, which I assume is because $libdir no longer
> references the build file system:
>
> <stdin>:3: Initializing the cluster
> <stdin>:5: PGRES_FATAL_ERROR load '$libdir/xxid';  - ERROR:  could not
> access file "$libdir/xxid": No such file or directory

You have to copy the xxid.so and slony1_funcs.so files to where postgres
extensions live on your target machine. on debian this seems to be
/usr/lib/postgres/lib/

this is the same place where you can find various pl implementations
find /usr/lib -name plpgsql.so
should show you the place

------------
Hannu