Jacques Caron wrote:
>> this just a limitation of slony? Or is there a workaround I've missed?
> 
> What other option would you imagine there could be?
> 

Reject Master db connections.  Dump Master.  Load Master data onto 
Slave.  Start Master/Slave replication.  Re-allow Master DB connections.

I would imaging that there'd need to be some sort of seeding operation 
in between the data load and the starting of the master and slave 
replication, where one populates the slony tables with the sync status 
of each of the tables/sequences in the set.

Obviously that's not something that is supported, but that was kinda 
what I had in mind when I started.

Rob