Mon Nov 10 17:42:08 PST 2008
- Previous message: [Slony1-general] truncate failed???
- Next message: [Slony1-general] best way to verify slony is properly syncing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 10 Nov 2008, Geoffrey wrote: > I've received the message: > > NOTICE: truncate of "public"."foo" failed - doing delete > > When first initializing slony on a slave where all the tables are empty. Why > would the truncate fail on an empty table? Because of foreign key references from other tables. From the docs: TRUNCATE cannot be used on a table that has foreign-key references from other tables, unless all such tables are also truncated in the same command. Checking validity in such cases would require table scans, and the whole point is not to do one. -- Jeff Frost, Owner <jeff at frostconsultingllc.com> Frost Consulting, LLC http://www.frostconsultingllc.com/ Phone: 916-647-6411 FAX: 916-405-4032
- Previous message: [Slony1-general] truncate failed???
- Next message: [Slony1-general] best way to verify slony is properly syncing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list