Hi,

I've tried Slony-I 2.0.3RC2 with out PostgreSQL 8.3 database and it
throws errors in the Log:

NOTICE:  Slony-I: Logswitch to sl_log_2 initiated
CONTEXT:  SQL statement "SELECT  "_test_cluster".logswitch_start()"
PL/pgSQL function "cleanupevent" line 101 at PERFORM
2009-11-02 11:23:56 CET INFO   cleanupThread:    0.004 seconds for
cleanupEvent()
2009-11-02 11:23:56 CET ERROR  cleanupThread: "select nspname, relname
from "_test_cluster".TablesToVacuum();" - ERROR:  function
_test_cluster.shouldslonyvacuumtable(name, name) does not exist
LINE 1: SELECT  "_test_cluster".ShouldSlonyVacuumTable( $1 ,  $2 )
                ^
HINT:  No function matches the given name and argument types. You might
need to add explicit type casts.
QUERY:  SELECT  "_test_cluster".ShouldSlonyVacuumTable( $1 ,  $2 )
CONTEXT:  PL/pgSQL function "tablestovacuum" line 6 at IF
2009-11-02 11:23:56 CET INFO   cleanupThread:    0.001 seconds for vacuuming

After investigating I found out that in slony1-funcs.sql revision
1.145.2.13 the function ShouldSlonyVacuumTables was removed [1]. It
looks like it was moved to slony1-funcs.v84.sql but not to
slony1-funcs.v83.sql.

In Slony-I 2.0.2 this was still working, unfortunately I was forced to
try the RC2 because transactions longer than 10 Minutes completely break
replication in the old version.

Will there be a new release anytime soon? And if not, would there be
side effects if I simply fix it myself by putting the missing function
in slony1-func.v83.sql? I would really like to use Slony in a production
environment but so far I didn't get it to work reliably in my tests. :-(

Regards,
Gwyn

[1]
http://main.slony.info/viewcvs/viewvc.cgi/slony1-engine/src/backend/slony1_funcs.sql?r1=1.145.2.12&r2=1.145.2.13&pathrev=REL_2_0_STABLE&diff_format=h