Chris, Christian,

> > That table will presumably need a VACUUM FULL when you get a chance.
> > (That will slow replication while it's running, but shouldn't have much
> > impact on users; it doesn't block inserts into replicated tables...)
>
> Will try, but I'm afraid that something is still blocking on the table.
>
> BTW, what process is it that requires an ExclusiveLock on pg_listener?

OK, successive VACUUMs took care of it; I just had to VACUUM around the timing 
of Slony locking pg_listener.

Obviously we need to vacuum the Slony schema a lot more frequently ....

--Josh

-- 
__Aglio Database Solutions_______________
Josh Berkus		       Consultant
josh at agliodbs.com	 www.agliodbs.com
Ph: 415-752-2500	Fax: 415-752-2387
2166 Hayes Suite 200	San Francisco, CA