Tue Jun 10 11:13:01 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 ]
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. -- (reverse (concatenate 'string "moc.enworbbc" "@" "enworbbc")) http://www3.sympatico.ca/cbbrowne/rdbms.html "... While programs written for Sun machines won't run unmodified on Intel-based computers, Sun said the two packages will be completely compatible and that software companies can convert a program from one system to the other through a fairly straightforward and automated process known as ``recompiling.''" -- San Jose Mercury News
- 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