Highly doubtful. The process is pretty much exactly what is on the 
intro documentation, and goes like so:


export CLUSTERNAME=slony_test
export MASTERDBNAME=bench
export SLAVEDBNAME=bench2
export MASTERHOST=localhost
export SLAVEHOST=localhost
export REPLICATIONUSER=postgres
export DBUSER=bench

createdb -O $DBUSER -h $MASTERHOST $MASTERDBNAME
createdb -O $DBUSER -h $SLAVEHOST $SLAVEDBNAME

echo "create table foo (id serial primary key);" | psql $MASTERDBNAME
echo "create table foo (id serial primary key);" | psql $SLAVEDBNAME

createlang plpgsql -h $MASTERHOST $MASTERDBNAME
createlang plpgsql -h $MASTERHOST $SLAVEDBNAME

....and from there, I follow the intro docs at 
http://gborg.postgresql.org/project/slony1/genpage.php?howto_basic.

Well, with the change of fixing the typoo in the initial slonik script. :)


If there were some uncommitted transaction, how could I tell?

On Mon, 30 Aug 2004, Jan Wieck wrote:

> That isn't the error. The remote worker thread will not be there until 
> there is a subscribed set to sync, not to copy. The warning is coming 
> from a generic function that is called to wake one up if it exists.
> 
> I am pretty sure that you have some open connection. Are you for example 
> connected to the DB with some other admin tool, like phppgadmin or the 
> like? Is there any chance that some OTHER database under the same 
> postmaster has connections that use bogus autocommit functionality?