On Thu, Oct 01, 2009 at 04:20:52PM +0700, stuart at stuartbishop.net wrote:
>
> EXECUTE SCRIPT wants to lock all tables, despite me being a
> consenting adult who promises not to muck with tables outside of the
> specified SET ID set.

[…]

> Are there other alternatives, such as a version of EXECUTE SCRIPT
> that has less paranoid locking behavior?

In the Old Days of Slony, EXECUTE SCRIPT locked the tables in the set,
not all tables.  It was changed because there was no way to prevent
people from inflicting self-damage.  I suppose you ought to be able to
re-patch the modern code with something like the old version.

I recall feeling somewhat equivocal about this change, precisely
because it would forestall exactly the sort of thing you are now
trying to do.

I seem to recall doing something similar with bare metal functions,
however, so you may be able to get around this just by not using
EXECUTE SCRIPT.

A

-- 
Andrew Sullivan
ajs at crankycanuck.ca