On Wednesday, February 12, 2014 11:14:17 PM Hanselman, Matthew wrote:
> The high-level requirement is: we need a way to isolate DDL changes and
> control them more tightly than data changes. 

Well, the right answer is, don't give devs the privileges needed to make DDL 
changes. 

If you're using Slony you probably need to do this anyway just to prevent them 
from making DDL changes directly, and to keep them from running ORM 
migrations. If your devs do currently have this access, you should check the 
schema differences between the master and slaves and find out what all they've 
already broken.

But yeah I don't think Slony will do what you're asking, regardless. You can't 
make data and schema changes happen out of order.