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


Devrim GUNDUZ <devrim at commandprompt.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |devrim at commandprompt.com




--- Comment #5 from Devrim GUNDUZ <devrim at commandprompt.com>  2009-04-10 09:02:25 ---
I think I hit something similar today.

I added a new set/table to existing replication. First edited slon_tools.conf,
and then ran slonik_create set and slonik_subscribe_set . 

It worked fine. 

The next step was merging set 999 (existing set) with set 3 (the one that I
just created). After merging set, replication stopped.

Here is a part of the log:

=======================
2009-04-10 03:00:46 PDT [11553] DEBUG2 remoteWorkerThread_2: all tables for set
3 found on subscriber
2009-04-10 03:00:46 PDT [11553] DEBUG2 remoteWorkerThread_2: copy sequence
"public"."rev_marketmap_pk_marketmap_id_seq"
2009-04-10 03:00:46 PDT [11553] ERROR  remoteWorkerThread_2: "select
"_replica".setAddSequence_int(3, 2015,
'"public"."rev_marketmap_pk_marketmap_id_seq"', 'Sequence
public.rev_marketmap_pk_marketmap_id_seq')" PGRES_FATAL_ERROR ERROR:  Slony-I:
setAddSequence_int(): sequence ID 2015 has already been assigned
2009-04-10 03:00:46 PDT [11553] WARN   remoteWorkerThread_2: data copy for set
3 failed - sleep 60 seconds

=======================

...and we are currently far behind replication.

This is Slony-I 1.2.10 on Linux.


-- 
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.
You are the assignee for the bug.