I am attempting to work with a test database structure; I have two test
servers, both of which are running SuSE 9.3, PostgreSQL 8.1.3, and Slony 1.1.5.
I created the databases yesterday evening, giving them both the same schema,
and allowed the first one to fill overnight (I'm trying to work with data from
another, production, db, my boss hopes to set up replication on it across our
network in the near future). This morning I attempted to replicate the data
from the first to the second, following the instructions in the Slony-1
Replication Tutorial. The data appears to have replicated at least once; the
formerly empty db now has the same data in it as the filled one had.
The next step I tried, however, was to run a delete statement. The end
result was to remove almost eight million records from a table on the primary
db. (I expected this number; there were about fifteen million records on the
table to begin with, and I used a fairly common value in my filter.) The two
slon instances appear to still be running, but they do not appear to be
communicating any longer; it has been two hours since the delete ended, and I
am not seeing any sign that the results of the delete are being replicated.
I've replicated delete statements on smaller db's while trying to teach myself
how to set up replication, so I know it can be done.
Does anyone have any advice as to how I can check to ensure that my delete is
getting replicated? I admit that the original delete statement may have been a
bit overboard in its scope, but I'd like to make sure I've got everything
working.
Thank you for your consideration.
---------------------------------
8:00? 8:25? 8:40? Find a flick in no time
with theYahoo! Search movie showtime shortcut.
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
