http://www.slony.info/bugzilla/show_bug.cgi?id=217

--- Comment #6 from Christopher Browne <cbbrowne at ca.afilias.info> 2011-05-30 08:45:00 PDT ---
There exist arguments both ways:

1.  Only running this against tables that already have locks taken out means
we're not escalating locks, and we can indeed be confident that any tables that
are being modified in *THIS* DDL script will already be locked.

2.  If we don't fix all tables that need fixing, then we're leaving a broken
state in place.  The DDL request may demand some locks that it didn't already
have, but only against tables that probably can't replicate properly.  Doesn't
that seem like a high priority fix???

I'd be inclined to fix all tables that need fixing, otherwise, replication
remains broken for those tables.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.