Home > Archive > Slony1 PostgreSQL Replication > February 2006 > cleanupNodeLock









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author cleanupNodeLock
lkv

2006-02-13, 9:24 am

I get occasional failures at cleanupNodeLock:

localListenThread: "select "%namespace%".cleanupNodelock(); insert
into "%namespace%".sl_nodelock values ( 3, 0,
"pg_catalog".pg_backend_pid()); " - ERROR: duplicate key violates
unique constraint "sl_nodelock-pkey"

i get to clean the stale lock by hand. from a brief glance i see no
obvious reason why the function will fail.

setup is with slony1-1.1.5 and postgresql 7.4, 1master/2 slaves. but
so far the above happened only on the one of the slaves. the setup is
as follows:

m1
master
runs slon for slavedb on m2
runs slon for master

m2
slavedb
<slon for this database is actually running on m1>

m3
slavedb
runs slon for slavedb

do you think that setup might've been causing the problems?
any hints would be appreciated!

thanks in advance,
l
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com