On Fri, Feb 22, 2008 at 09:18:59AM -0600, Troy Wolf wrote:
> Therefore, running execute_script will LOCK ALL TABLES IN ALL REPLICATION
> SETS regardless. Correct?

Yes.  Not all of us agree with that decision, by the way, but that's how
it's implemented now.
 
> Now onto my issue at hand: Twice now, we've seen a pattern that looks like
> Slony is waiting on a large index creation to complete, and then an
> application gets stuck waiting behind Slony's locks. 
[. . .]
> At this point in time, I'm not 100% sure the application commit was blocked
> by Slony except we never had this problem before Slony.

I'm not dismissing your description, but output from pg_locks would be
helpful here.  Without a specific case, it's hard to say much more.

A