Tue Aug 19 02:41:45 PDT 2008
- Previous message: [Slony1-general] RE: duplicate key value violates unique constraint "sl_nodelock-pkey"
- Next message: [Slony1-general] Random Duplicates Error
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
hi everyone, I have a problem with one of our current slony clusters. The cluster consists of one origin and 3 subscribers all running Slony1 v.1.2.14 and PostgreSQL v.8.3.3 on Debian Etch. There are around 3 mil. rows in one big table that are deleted and newly inserted on a daily basis. Every now and then (around once a week) one (any of them) of the subscribers fails to replicate the origin's data with the following message in the log: ERROR: duplicate key value violates unique constraint "xyz" There is no further indication in the logs what could have been the cause for this problem. 1) is this a known problem that the replication may fail occasionally when there are lots of insert's going on? Any suggestions on what I could do to prevent this from happening? 2) what's the preferred workaround for such a situation? right, now I'm just dropping the corresponding node and re-create it from scratch. cheers, tom. PS: other clusters on the same hosts don't never have such problems but they also don't have that many deletes/inserts going on.
- Previous message: [Slony1-general] RE: duplicate key value violates unique constraint "sl_nodelock-pkey"
- Next message: [Slony1-general] Random Duplicates Error
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list