http://www.slony.info/bugzilla/show_bug.cgi?id=35


David Rees <drees76 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |drees76 at gmail.com




--- Comment #9 from David Rees <drees76 at gmail.com>  2008-02-18 20:33:34 ---
FWIW, here is my experience with this bug:

I am in the process of upgrading my test cluster from Pg 8.2 to 8.3, so the
first step was installing Slony 1.2.13 which has Pg 8.3 support.

After compiling (./configure --pgconfdir=/usr/local/pgsql/bin/pg_config
--prefix=/usr/local/slony-1.2.13-2008021800 --with-perltools) and installing
Slony (make install), I then proceeded to upgrade the slony schemas using
slonik_update_nodes after shutting down old slon daemons.

But it failed with this error:

# slonik_update_nodes | slonik
<stdin>:3: could not open file
/usr/local/slony-1.2.13-2008021800/share/slony1_funcs.sql

I found slony1_funcs.sql in pgsql/share which is apparently where it used to
live.

I temporarily worked around this issue by copying all the slony scripts to the
slony/share folder.

Regardless of where the scripts should live, at the very least with a simple
install like this slony should find the scripts wherever they happen to be.


-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.