| Victoria Parsons 2005-08-22, 7:25 am |
| I think I may have solved this. I have subscribed the node many times,
and deleted, then resubscribed. I traced the SQL line back to an insert
into sl_path that was failing because the pair of provider and receiver
already existed. I have run my unsubscribe script and it does remove
this line, but maybe the time I got this error I had not fully removed
the node before I tried to add it again.
So thanks, but I hope I can sort this out on my own now.
Vicki
____________________
____________
From: slony1-general-bounces- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
[mailto:slony1-general-bounces- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org] On Behalf Of
Victoria Parsons
Sent: 22 August 2005 09:53
To: slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
Subject: [Slony1-general] subscribeSet error
Hi,
I've a got a problem with subscribe set. I have done a set up with this
configuration in the past so I don't think it is my parameters (dbname
etc) that are wrong. I am settings up node number 3, where the origin is
node 1.
This is the error I get:
<stdin>:21: PGRES_FATAL_ERROR select "_sss_repcluster".subscribeSet(1,
1, 3, 'f'); - ERROR: duplicate key violates unique constraint
"sl_path-pkey"
CONTEXT: PL/pgSQL function "subscribeset_int" line 48 at SQL statement
PL/pgSQL function "subscribeset" line 60 at perform
ERROR launching node
This is my script:
sssname, csgname and nodenum are already defined in the script
(nodenum=3)
SSSCONNINFO="'dbname=sss host=$SSSNAME user=postgres'"
CSGCONNINFO="'dbname=sss host=$CSGNAME user=postgres'"
slonik <<_EOF_
#-----------------------------------------------------------------------
--------
# define the namespace the replication system uses
#-----------------------------------------------------------------------
--------
cluster name = sss_repcluster;
#-----------------------------------------------------------------------
--------
# admin conninfo's are used by slonik to connect to the nodes.
# There is one entry for each node in the cluster, the syntax is that of
PQconnectdb in
# the C-API
#-----------------------------------------------------------------------
--------
node 1 admin conninfo = $SSSCONNINFO;
node $NODENUM admin conninfo = $CSGCONNINFO;
#-----------------------------------------------------------------------
--------
# Subscribe the new node to the set
#-----------------------------------------------------------------------
--------
subscribe set (id = 1, provider = 1, receiver = $NODENUM, forward =no);
wait for event (origin = all, confirmed = all, wait on = 1);
_EOF _
The error seems to be a problem with the internal subscribeset_int
function. I am using slony 1_1_0-rc1. Will it be fixed if I get the
latest release, or is it something I'm doing wrong?
Cheers,
Vicki
This message should be regarded as confidential. If you have received
this
email in error please notify the sender and destroy it immediately.
Statements of intent shall only become binding when confirmed in hard
copy
by an authorized signatory.
This message has been scanned for viruses and potentially harmful
content by StreamShield Protector <http://www.streamshield.com/> .
--
This message has been scanned for viruses and potentially
harmful content by StreamShield Protector.
|