Jan Wieck wrote:

> The problem is that after the failover, the information to which SYNC
> point the old slave had already applied the changes is lost. There
> might be older than that update information in sl_log_1.

Thankfully the very first statement is an insert for what would have
been the next ID in a table; so it looks like it sl_log_1 was up to
date. We're just lucky we even have the slony tables (I did not know
they were being backed up!).

> If this was a 1.1 Slony, lets see.
>
> 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. The resulting SQL
> scripts are all yours.

This sounds like an excellent plan. The previously suggested SQL
approach was producing results, but getting slony to do the work for me
is appealing.

Thanks.