Fri Jul 17 13:18:25 PDT 2009
- Previous message: [Slony1-general] How to downgrade from 2.0.2 to 2.0.1
- Next message: [Slony1-general] How to downgrade from 2.0.2 to 2.0.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Devrim GÜNDÜZ wrote: > > What kind of issues? I think reporting them and asking them to be fixed > could be better for you (and everyone in the planet) > Issue 1: After a successful initial copy of a set, it starts getting this error: ERROR: duplicate key value violates unique constraint "text_metrics_pkey" continuously when doing updates to a table in the set it just synced. I repeated this exact behavior on another node by unsubscribing the set and resyncing it. I had to unsubscribe the set everywhere. Issue 2: After a successful initial copy of a different set, it starts getting this error: 14 0717 10:45:01 CONFIG slon: child terminated status: 11; pid: 28356, current worker pid: 28356 ..and then it restarts the worker process. This repeats indefinitely every 10 sec until I unsubscribe the set from the node. Regards -- View this message in context: http://www.nabble.com/How-to-downgrade-from-2.0.2-to-2.0.1-tp24540512p24540853.html Sent from the Slony-I -- General mailing list archive at Nabble.com.
- Previous message: [Slony1-general] How to downgrade from 2.0.2 to 2.0.1
- Next message: [Slony1-general] How to downgrade from 2.0.2 to 2.0.1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list