Tue Jun 10 11:30:41 PDT 2008
- Previous message: [Slony1-general] truncate of "public"."foo" succeeded
- Next message: [Slony1-general] truncate of "public"."foo" succeeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Christopher Browne wrote: > Geoffrey <lists at serioustechnology.com> writes: >> I don't remember seeing these messages before, maybe I'm >> wrong. Question is, the node 2 database I'm replicating to, is already >> empty. Does slony simply try a wholesale truncation of all replicated >> tables anyway? > > Yes, it does, in order to make *sure* that it's starting with a clean > slate. > >> Also, I see a couple messages like these: >> >> truncate of "public"."foo" failed - doing delete >> >> I don't understand why the truncation would fail. > > That normally happens because Slony-I found a foreign key constraint > that prevented TRUNCATE from working. No big problem. Thank you both Chris and Bill. -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
- Previous message: [Slony1-general] truncate of "public"."foo" succeeded
- Next message: [Slony1-general] truncate of "public"."foo" succeeded
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list