Richard,

Have you included the sequences for the tables in the replication
config?
EG: 
SET ADD SEQUENCE ( SET ID=2, ORIGIN=1, ID=2001, FULLY QUALIFIED
NAME='your_schema.table_name_table_col_seq',
COMMENT='table_name_table_col_seq');

?
You need a SET ADD SEQUENCE for _every_ sequence you want replicated.


-----Original Message-----
From: Richard Yen [mailto:dba at richyen.com] 
Sent: Tuesday, June 27, 2006 10:37 AM
To: cbbrowne at ca.afilias.info
Cc: Melvin Davidson; slony1-general at gborg.postgresql.org
Subject: Re: [Slony1-general] How does slony track sequences

Darn, I was hoping for a different answer.

Just happened to run into this recently...  When I do a MOVE SET, the
new master's sequences seem to get reset, or they were never updated at
all.  New INSERTS get a 'duplicate key violates primary key constraint'
message...

--Richard


On Jun 26, 2006, at 8:30 PM, cbbrowne at ca.afilias.info wrote:

>> How does slony replicate sequences?
>>
>> I am aware that slony monitors changes to tables by creating triigers

>> on each table in the replication set. I see no trigger or rules for 
>> sequences that are replicated.
>> How does slony keep track of sequences>
>
> Quite simply: By polling.
>
> It records current value at each SYNC...
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>
>