On Sat, Feb 23, 2008 at 10:28:57AM -0800, Craig James wrote:
> 
> You tell me?  It is the slon daemon that is executing this select.  There 
> were no other connections to the database the second time I tried this.

[. . .]

> withstand being killed without corrupting data.  Besides, I had no choice, 
> my web site went offline because slon apparently took an exclusive lock on 
> the tables, blocking all other activity.  And I killed a SELECT, not an 
> INSERT or UPDATE.

So your website is offline the second time you tried this?

Slony will indeed take an exclusive lock blocking all other activity, and if
something is in line ahead of it, you're going to have a problem.  I think I
already suggested that your problem would be much easier (read "possible")
to diagnose with some data from pg_locks.

A