On Thu, Jan 27, 2005 at 10:02:05AM -0700, Brian Hirt wrote:
> I hope I'm just doing something stupid, and there is an easy solution 
> to this problem.   We currently run slony 1.0.5 and postgres 7.4.6 on 
> linux 2.4 systems.  I look  forward to any advice people might have.  
> It seems like part of the problem stems from the fact that all tables 
> in the set are locked by slon during this process, even if only one 
> table is being updated by the execute script (ref; 
> http://cbbrowne.com/info/stmtddlscript.html). 
>

I also have major problems with deadlocks while trying to do
EXECUTE SCRIPT changes, both on the master and on busy read-only
slaves (causing slon processes to die, etc).

While you probably shouldn't do index changes through slonik, actual tables
changes are very problematic at best.

Anything that can be done to improve this would be appreciated.

-- 
"Government big enough to supply everything you need is big enough to take
everything you have ... the course of history shows that as a government
grows, liberty decreases." -- Thomas Jefferson