Tue Jun 10 11:16:25 PDT 2008
- Previous message: [Slony1-general] truncate of "public"."foo" succeeded
- Next message: [Slony1-general] FATAL error in log
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In response to Geoffrey <lists at serioustechnology.com>: > 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. Slony doesn't trust the user to have a properly cleaned out database, which (IMHO) is A Good Thing. > Also, I see a couple messages like these: > > truncate of "public"."foo" failed - doing delete > > I don't understand why the truncation would fail. >From the PostgreSQL docs: RESTRICT Refuse to truncate if any of the tables have foreign-key references from tables that are not to be truncated. This is the default. -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ wmoran at collaborativefusion.com Phone: 412-422-3463x4023
- Previous message: [Slony1-general] truncate of "public"."foo" succeeded
- Next message: [Slony1-general] FATAL error in log
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list