Sorry this took so long, but yes, I have a script that explicitly runs a SET ADD SEQUENCE and a SET ADD TABLE for each sequence and table in the set.
However, I recently tried this on a dev environment, and the sequences get moved properly when I do the MOVE SET. So, I guess there must be something wrong with my script. I'll keep looking into this one. If this happens again, I'll post another message. Thanks for the help! --Richard On Jun 27, 2006, at 2:39 PM, Alan Hodgson wrote: > On Tuesday 27 June 2006 09:36, Richard Yen <[EMAIL PROTECTED]> wrote: >> 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... > > You would have had to explicitly add them to your set. Did you? > > > -- > Who are you working for? The average Canadian family pays 47% of > their total income in taxes. If you and your spouse both work, one > of you is working for the government and the other is working for > your family. > _______________________________________________ > Slony1-general mailing list > [email protected] > http://gborg.postgresql.org/mailman/listinfo/slony1-general _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
