SLONY DDL errors
Slony version 1.1.2
If executing a slony DDL script that contains a "DROP TABLE" statement
fails with errors, and the exact cause is
not immediately known, try executing the DDL commands through a SQL window.
If the DROP commands succeed on the MASTER, but fail on the SLAVE with
an error similar to
ERROR: "xxxx_pk" is an index
Then the problem is caused by the table being deleted having a
constraint that refers to the primary key of another
table that is being replicated.
To resolve the problem:
1: Drop any tables from the slony replication set that are referred to
by the table being DROP'ed.
ie: SET DROP TABLE ( ORIGIN=nn, ID=xxx); (where nn is the set # and
xxx is the id of the table):
2. After completing the DDL statements, re-add the tables to the
replication set(s) with MERGE SET.
begin:vcard
fn:Melvin Davidson
n:Davidson;Melvin
org:Computer & Communication Technologies
adr;dom:;;6 Inverness Ct. East;Englewood;CO;80112
email;internet:[EMAIL PROTECTED]
title:Database Developer
tel;work:303-708-9228 ext. 305
x-mozilla-html:TRUE
url:http://www.cctus.com
version:2.1
end:vcard
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
