Jan Wieck wrote:

> I would create a similar setup on test systems. Just identical schema,
> no data. Stop both slon's once the subscribe is complete. data-only
> dump and resture the current master into the test-slave. Data-only
> dump and restore the test-masters slony tables sl_event and sl_log_1
> with the contents from your dump (the partial one from the old
> master). Now hack sl_confirm and sl_setsync on the test-slave so that
> it matches the desired first SYNC to pick up and start the test-slave
> slon process with the file-log-shipping option. 

Something's not quite working for me here; no data is being updated (I
am trying to send to the slave db rather than log files -- hope that's
not a problem).

Do I need to hack the sl_* tables on the slave to make sure that the
tables and sets match the original replication table IDs etc?